The funny thing about the agile manifesto is that it doesn't actually say anything remotely related to process.
It basically states a set of attributes your process should exhibit.
Agile as I have experienced it in practice almost never displays those attributes.
The whole thing makes very little sense. I mean read it.
>"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."
How the hell do you get from that to where we are today?
What it ought to say is:
"We value short feedback loops that minimize risk and maximize learning.
We value flexibility.
We welcome change.
We don't know what we are doing, only what we intend to do. The outcome is a guess. Our guesses could always be better. We strive to make them so."
