Time and again, people have delivered exceptional work in human civilization. And to get work done, they had practices.
Initially, these practices were developed out of the trial and error method. And, later on, became management theories which are still applied in big enterprises.
Similarly, in the 1950s, a relatively new field originated, which was coined as Software Engineering as an alias for Software Development.
And, in 1956 Herbert D. Benington started writing the first way to build software.
Later in the 1970s, Winston W. Royce wrote a formal paper from which the Waterfall model for software development was mistakenly drawn. And, went on to become the first and most popular software development framework – The Waterfall Methodology.
The waterfall methodology focuses on completing each phase of development before the next phase starts. The waterfall development framework is sequential, prescriptive, and documentation intensive. Though the waterfall model was popular, it was process-heavy and unresponsive to changes.
The software industry realized a need for an alternate approach, mainly because of three primary reasons
- Technology was rapidly changing
- Constant demand to update the product based on changing technology
- A need for a faster development approach
This rapid need for a change in the software industry led 17 software practitioners to come together in 2001 to discuss an alternative software development approach that should address the problems of existing models.
Most of the participants individually had tried out different processes successfully. As each process had its own advantages, they decided on not selecting a better approach or combining their ideas, instead focused on identifying a generic term that describes everyone’s ideas to set a standard for software development.
And thereby the birth of the Agile Manifesto.