The publication of lean-software-development-agile-toolkit-2003 by addison-wesley in 2003 was the founding moment of lean software as a recognized approach within the Agile ecosystem. It was the first systematic translation of TPS principles into software development practice, and it gave mary-poppendieck and tom-poppendieck the platform from which all subsequent work followed.
What the Book Established
The book did several things simultaneously. It introduced the seven-lean-principles as a coherent framework — eliminate waste, amplify learning, decide late, deliver fast, empower the team, build integrity in, optimize the whole — giving lean software a clear intellectual structure. It introduced the seven-wastes-of-software taxonomy, which became the most frequently cited element of Poppendieck work. And by appearing in the Addison-Wesley Agile Software Development Series alongside the XP and Scrum books, it positioned lean software as a peer contribution to the Agile canon rather than an alternative to it.
Context
The book appeared two years after the agile-manifesto-2001, when the Agile community was consolidating around Scrum and XP but actively looking for complementary frameworks. The Poppendiecks' timing was favorable: the audience existed, the credibility problem had been partially solved by the Manifesto community's prior work, and the lean manufacturing source material was well-developed enough (through Womack and james-womack's lean-enterprise-institute work) to support a rigorous translation.
Legacy
The 2003 book created the lean software category and established the Poppendiecks as its primary architects. It led directly to implementing-lean-software-development-2006 and leading-lean-software-development-2009, and its frameworks influenced david-anderson's Kanban development, the lean startup movement, and practitioners like gene-kim who applied lean thinking to IT operations and DevOps.