The points above clearly illustrate the failure of earlier methodologies like water fall, spiral etc. one may think why did these why did these work in the past, well the basic reason is that things happen much faster not then it did in the past. MS took years to come up with a new version of office 97 and then 2000 and now they plan to do that practically every year, same is true for many of there products. Customers are now more informative and want to move with the fast paced world.
Agile - Introduction
During the 90s a number of different people realised that things had somehow changed. These people became interested in developing software methodologies that were a better fit with the new business environment – more nimble, easier to manoeuvre through a turbulent business environment. Although the details of these methodologies differ, they all share certain underlying principles, to the extent that these methodologies are often now grouped under the title “agile methodologies”.Given the opportunity to reject the “software engineering” metaphor and start all over again, what would we consider as we were developing a new methodology?·
- Software development is predominantly a design activity·
- Characteristics of individuals are the first-order influence on project activities·
- Modern software development can't rely on individuals – it requires effective teams·
- Customers are unlikely to know what they want in detail before they start·
- Customers need to be able to change requirements without unreasonable penalties·
- The process needs to be flexible·
- Responsibility should be aligned with authority
I am still a student of agile and will be writing more about it in the future.