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.
aka Faux Agile or Evil Agile
https://ronjeffries.com/articles/018-01ff/abandon-1/
this obeys Chaffee's Law of Titles: if a discipline's title includes a complimentary descriptor, then that descriptor does not apply
Why is it called "extreme"? Mostly it's tongue-in-cheek, but beneath that is an honest experiment:
Instead of saying "we should really do X..."
(and then not)
...what if we do X all the time ?
(where X is testing, code review, incremental design, refactoring, ...)
The most efficient way to answer the question,
"What will today's weather be?"
is with the question,
"What was the weather yesterday?"
...sure it'll be wrong 20% of the time, but that's a much better rate than every other planning system
First learn the rules
then obey the rules
then improve the rules
(then repeat)
see cadence and retrospectives lessons
1/18