The Four Values
The four value statements are comparisons, not commands to discard everything on the right. Agile teams still use processes, tools, documentation, contracts, and plans. They value people, working results, collaboration, and responsiveness more when the two sides compete.
The closing sentence matters: the items on the right still have value. The practical skill is noticing a trade-off and choosing the side that improves learning and delivery in the present context.
Reading
coreRead the values as trade-offs
The Manifesto values individuals and interactions over processes and tools; working software over comprehensive documentation; customer collaboration over contract negotiation; and responding to change over following a plan.
The closing sentence prevents a common distortion: the items on the right still have value. A team needs tools, useful documentation, agreements, and plans. The values tell the team what to favor when the two sides conflict and which choice is more likely to preserve learning and useful delivery.
Outside software, read “working software” as a usable result. The test is whether someone can obtain value and provide evidence—not whether the team produced a large volume of internal activity.
References
Reading
coreRead the canonical Manifesto
The authoritative four value statements and closing sentence remain available at agilemanifesto.org. Read them at the source, then return to the matcher and notice that each statement preserves value on both sides while expressing a priority.
References
Interaction
corePractice · matcher
Match a situation to the value it tests
Choose the value-side that should receive greater emphasis in each trade-off.
Concepts: four values, contextual trade-offs
Activity ready. Attempts are unlimited and do not affect certificate eligibility.
Equivalent non-interactive path
Read fmap-m1-l2-digest; it teaches the same matching relationships without interactive controls.