Radical Premise

Back in 2001, seventeen software developers came together to share their stories of how how they were re-imagining how software could be developed.

In that gathering, they found a common understanding and crafted a Manifesto to express it.

They coined the term "Agile" for their movement and named their manifesto the Agile Manifesto :

>We are uncovering better ways of developing software by doing it and helping others do it. >Through this work we have come to value: >**Individuals and interactions** over processes and tools **Working software** over comprehensive documentation **Customer collaboration** over contract negotiation Responding to change over following a plan >That is, while there is value in the items on the right, we value the items on the left more.

Along with the Manifesto, 12 Principles were defined. Here is where the radical nature begins to be revealed.

The last two Principles are, arguably, the most radical:

>The best architectures, requirements, and designs emerge from self-organizing teams. >At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

Both of these Principles fundamentally challenged the paradigm of Scientific Management of the Industrial Age and called forth a new model of Value Creation.

Learn more about The Agile Story