The title is a quote taken from the Agile Manifesto’s co-founders Martin Fowler and Jim Highsmith who’s approach to software development is completely different to traditional software development such as the Waterfall. So in my previous post I just posted really on the basic aspects of the waterfall model and to continue from that post I’ll focus really on what are the limitations of this form of software development in comparison to the agile manifesto. It is the ability to respond to change that often determines the success or failure of a software project. Heavyweight (Traditional) methods freeze product functionality and disallow change. However one of the key, philosophical constructs making agile processes successful in today’s market is its response to change at any stage of the project. It makes it very difficult to implement a predictive process or to provide a set of stable requirements in this volatile and constantly changing environment. While Waterfall may be easy to manage due to the rigidity of the model and the phases are being processed and completed one at a time. However, adjusting scope during the life-cycle can kill a project, no working software is produced until late during the lifecycle and it includes high amounts of risk and uncertainty. It doesn’t exactly abide by the mantra of Michael Dell who states that in software development, “..the only constant is change”.
The video below is one I found on YouTube which I found really informative as it gave a good idea on how companies choose a form of software development!