top of page
Writer's pictureThe Agile Wiz

How the Agile Manifesto came to be...

Updated: Jul 13, 2020


The Conception of the Agile Manifesto

The 1990's saw a huge number of frustrated developers and dissatisfied clients; it was not a happy time for them – we could even go as far as calling it the Dark Times of the Software industry. There was a huge gap between the client’s requirements and the product that the developers delivered. Making any changes at all meant huge delays and even higher expenses for the developers as well as clients.

Simply put, the Traditional methods of development were unable to keep up with the ever-changing demands of the customers which often led to the cancellation of projects and contracts.


If the 1990s taught us anything, it is that there was a dire need for an innovative and flexible methodology that can easily adapt and respond to the ever-changing environment in the industry.


The one good thing that came out of all this grief was the Agile Alliance. The Alliance first came into existence in the year 2001 (Snowbird, Utah), when a group of 17 software rebels came together to, once and for all, overcome the frustrations and inefficiencies that were very much a part of software development in the 1990's. This alliance made history by framing and signing arguably the single most important piece of document in the software world, that is, the Agile Manifesto.


What was meant to be a software development guide, very soon, turned out to be a doctrine or the ultimate guide for project management.


15 views0 comments

Recent Posts

See All

Comments


bottom of page