The Agile Manifesto was drafted and signed at Snowbird, Utah in February 2001 by 17 software development practitioners representing Extreme Programming, Scrum, DSDM, Adaptive Software Development, Crystal, Feature-Driven Development, and Pragmatic Programming. It articulated four values and twelve principles that defined a lightweight, adaptive alternative to the dominant heavyweight process models.
Relation to the Poppendieck Framework
mary-poppendieck and tom-poppendieck were not among the 17 signatories. Their significance to this event is indirect but substantial: the Agile Manifesto created the community context in which lean software development ideas would find a prepared audience.
The Manifesto's four values — individuals and interactions over processes and tools, working software over comprehensive documentation, customer collaboration over contract negotiation, responding to change over following a plan — are substantively aligned with lean thinking. The emphasis on flow, waste elimination, and learning that characterizes the seven-lean-principles framework addresses the how that the Manifesto largely left open. This complementarity meant that when lean-software-development-agile-toolkit-2003 appeared two years later, it was received not as a challenge to the Agile Manifesto but as a mechanism for implementing its values.
The Enabling Condition
The Manifesto's most important contribution to the lean software story was legitimation. By 2003, the Agile community had already established that the critique of heavyweight processes was credible and that lightweight alternatives were viable. The Poppendiecks did not have to argue for that premise; they could begin with it and argue for lean as the most principled instantiation of it. The agile-alliance that grew from the Manifesto provided the institutional home — conferences, networks, publications — through which lean software ideas spread.