The Agile 2003 keynote by mary-poppendieck and tom-poppendieck was one of their first major conference presentations introducing lean software development to the emerging Agile community, delivered the same year as lean-software-development-agile-toolkit-2003.
Context: The Agile Community in 2003
The agile-alliance had been founded in 2001 following the Agile Manifesto, and the early Agile conferences were the primary gathering point for practitioners of Scrum, XP, Crystal, and DSDM. By 2003, Scrum and XP had achieved significant practitioner adoption, but the theoretical underpinnings of why Agile methods worked remained underdeveloped. The Poppendiecks arrived at this moment with a framework — rooted in taiichi-ohno's Toyota Production System and w-edwards-deming's quality science — that could explain the Agile community's empirical insights in terms of manufacturing systems theory.
The keynote format gave mary-poppendieck and tom-poppendieck the opportunity to address the entire Agile conference audience, not just attendees of a specific session. This was significant: a keynote at Agile 2003 reached the community's early adopters and thought leaders, seeding the lean software vocabulary — the seven-lean-principles, the seven-wastes-of-software, amplify-learning — in the practitioner community at the moment the community was most actively forming its intellectual identity.
Content and Framing
The keynote introduced the core argument of lean-software-development-agile-toolkit-2003: that Agile practices are not arbitrary empirical discoveries but implementations of lean principles that Toyota had worked out over decades. The eliminate-waste framing was particularly resonant with Agile practitioners who were already arguing against unnecessary documentation, process overhead, and big up-front design — the Poppendiecks gave these intuitions a theoretical vocabulary.
The presentation also introduced the seven-wastes-of-software taxonomy, which gave Agile teams a systematic way to identify and articulate the waste that lean practice aims to eliminate. This was immediately applicable: practitioners could map their own processes against the waste categories and identify concrete improvement targets.
Significance for Reception
The Agile 2003 keynote was a pivotal moment in the reception of lean software development. By addressing the Agile community directly and framing lean as complementary to rather than competitive with Scrum and XP, the Poppendiecks positioned their work for rapid adoption within the community that would become lean software's primary carrier. Many of the practitioners who became lean software evangelists — and who later influenced david-anderson's Kanban work, gene-kim's DevOps practice, and the continuous delivery movement — encountered lean software for the first time at this or similar early Agile conference presentations.
The keynote demonstrates how the Poppendiecks understood community-building as integral to intellectual contribution: the ideas in the book needed a community of practice to implement them, and the conference keynote was the mechanism for seeding that community.