The principles beneath the practices.
WHAT IT IS
A set of values about how software is built, not a methodology.
WHAT THE VALUES EMPHASISE
People and interaction over process and tools Working software over comprehensive documentation Collaboration with customers over contract negotiation Responding to change over following a plan
WHAT THE PHRASING MEANS
The things on the right have value; the things on the left have more.
WHAT IT IS NOT
An excuse for no documentation An excuse for no planning A specific set of ceremonies Faster delivery of the same thing
WHAT IT ACTUALLY PROVIDES
Feedback, early and often, so the right thing is built.
WHAT THAT REQUIRES
Working software delivered frequently Real users giving real feedback Willingness to change direction Teams able to decide
WHAT ORGANISATIONS FREQUENTLY ADOPT INSTEAD
The ceremonies, without the feedback or the autonomy.
WHAT THAT PRODUCES
More meetings, and the same outcomes.
WHAT TO ASSESS
Whether feedback actually changes what is built.
WHAT THE TEST IS
When did you last change direction because of what you learned?
