Agile Manifesto

The Manifesto for Agile Software Development, published in 2001 by seventeen software practitioners at a Utah ski resort, is a four-sentence declaration of values that became the founding document of the agile software movement. It asserts: individuals and interactions over processes and tools; working software over comprehensive documentation; customer collaboration over contract negotiation; responding to change over following a plan. The manifesto was not a methodology but a value reversal — a deliberate inversion of the priorities that had produced the software crisis of the 1990s.

The historical irony is that the manifesto was a reaction against excessive process, yet agile itself became an industry of certifications, frameworks, and consulting practices that many of its signatories later disavowed. The document's power lies in its brevity; its vulnerability lies in the ease with which its values can be appropriated without its skepticism.

The Agile Industrial Complex and the Evasion of Power

The manifesto's most significant omission — and the one that enabled its wholesale capture by the consulting industry — is its silence on power. The phrase 'customer collaboration over contract negotiation' presupposes a symmetrical relationship between customer and developer, as if both parties arrive at the table with equal information, equal leverage, and equal ability to walk away. This is false in virtually every software development context. The customer typically controls the budget, the timeline, and the definition of success; the developer controls the technical means. 'Collaboration' in this context is not a neutral process. It is a negotiation disguised as a conversation, and the manifesto's framing makes the power asymmetry invisible.

The result was predictable. Agile was not adopted as a practice of software craft but as a methodology of project management, reinserting the very process it claimed to oppose under new names: Scrum masters instead of project managers, story points instead of man-hours, sprints instead of milestones. The Scrum framework, the SAFe methodology, and the certification industrial complex are not betrayals of agile. They are the logical consequence of a manifesto that refuses to name the structural conditions under which its values would be realized. A document that says 'individuals and interactions over processes and tools' without specifying how to prevent processes and tools from reasserting themselves is not a manifesto. It is a wish.

The deeper systems insight is that any set of values that does not include a theory of power will be captured by the existing power structure. This is not cynicism. It is the Iron Law of Bureaucracy applied to software development: the forms that are designed to serve a function will eventually be preserved even when the function is forgotten. The agile manifesto gave the software industry a vocabulary of rebellion without a theory of institutional change. It is no wonder that the rebellion was institutionalized.