The four values of the agile-manifesto are the most compressed statement of what the Agile movement stood for when the seventeen signatories gathered at snowbird-meeting-2001 in February 2001. Each value is stated as a preference, not an absolute rejection — "While there is value in the items on the right, we value the items on the left more." That qualifying clause is routinely dropped in popular accounts, and its loss has contributed substantially to dark-agile implementations that treat the right-hand items as forbidden.
The Four Values
Individuals and interactions over processes and tools. The humanistic core of the movement. See individuals-and-interactions for the full treatment. The signatories were reacting against a consulting and certification industry that sold processes as if organizational behavior were deterministic. alistair-cockburn's Crystal work and kent-beck's extreme-programming had both already demonstrated that team dynamics and individual skill mattered more than process compliance.
Working software over comprehensive documentation. The decisive break with waterfall's document-driven gating. See working-software. The critique was not that documentation has no value but that document production had become the primary organizational activity, with working software as a downstream byproduct. hirotaka-takeuchi and ikujiro-nonaka's new-new-product-development-game had shown that the highest-performing product teams shipped iteratively rather than through sequential document-then-build cycles.
Customer collaboration over contract negotiation. The recognition that requirements are discovered, not specified. Contracts attempt to fix scope, but software is a knowledge-creation activity in which neither the customer nor the developer knows at the outset what will actually be needed. This value connects directly to responding-to-change and to the lean concept of pulling requirements from customers rather than pushing specifications at them.
Responding to change over following a plan. The adaptive core. See responding-to-change for the connections to empirical-process-control, Boyd's OODA loop, and lean's last responsible moment concept.
The Structure of the Values
The paired structure — "X over Y" — was a deliberate rhetorical choice. It acknowledges trade-offs rather than asserting absolutes. This structure also reflects the intellectual diversity of the signatories: they could not agree on a single methodology, but they could agree on a common set of preferences. The values are framework-agnostic: scrum, extreme-programming, crystal, and dsdm each operationalize them differently.
Reception and Distortion
The four values have been interpreted in opposite directions. Practitioners in the post-agile-era critique the values as so abstract as to be meaningless — everyone claims to value individuals, working software, collaboration, and adaptability. Practitioners in the agile-industrial-complex have sometimes weaponized the values to dismiss legitimate concerns: "that's not Agile" applied to documentation, planning, or contracts. The qualifying clause ("while there is value...") is the antidote to both pathologies: the values express directional preferences, not categorical prohibitions.