The Agile 2007 keynote "The Role of Leadership in Software Development" by mary-poppendieck and tom-poppendieck was a significant conference presentation that foreshadowed the themes of their third book, leading-lean-software-development-2009, and signaled their evolving focus from lean practices to the organizational conditions that enable lean thinking.
Shift in Focus: From Practices to Leadership
By 2007, implementing-lean-software-development-2006 had been in the hands of practitioners for a year, and the lean software community had grown substantially. The patterns of failure were becoming visible: organizations that adopted lean vocabulary and lean tools without lean thinking at the leadership level were not achieving the results the framework promised. Teams could implement pull-systems-in-software, map value streams, and run iterative cycles — but if senior leaders continued to manage to output metrics, demand detailed up-front plans, and treat teams as interchangeable resources, the lean practices operated in a hostile context.
The 2007 keynote addressed this directly. mary-poppendieck and tom-poppendieck shifted their focus from "what should teams do?" to "what should leaders do?" — a reorientation that would define the entire third book.
The Leadership Argument
The keynote argued that leadership in lean software development requires a fundamentally different mental model than traditional software project management. Where conventional leadership manages to results (schedule, scope, budget), lean leadership manages to learning capacity — ensuring that teams have the feedback loops, decision authority, and psychological safety required to discover what works.
This is a direct expression of the learning-not-results thesis that would be enshrined in the subtitle of leading-lean-software-development-2009. The keynote was where the Poppendiecks first presented this argument to the Agile community at scale.
The empower-the-team principle, already articulated in lean-software-development-agile-toolkit-2003, received its leadership-level treatment: what organizational structures and leader behaviors actually enable team empowerment, versus paying lip service to it? The Poppendiecks examined the prerequisites — clear purpose, relevant information, appropriate authority, and developed judgment — and showed how most organizational empowerment initiatives fail because one or more prerequisites is missing.
Significance as Bridge
The Agile 2007 keynote is significant as the public bridge between the Poppendiecks' second and third books. It documents the intellectual development happening between implementing-lean-software-development-2006 and leading-lean-software-development-2009: the recognition that lean software implementation is bottlenecked not by team practice but by organizational structure and leadership behavior. The keynote let the Agile community track this evolution in real time, and the audience response — the problems practitioners recognized in their own organizations — shaped the framing of the 2009 book.
The talk also reflects the agile-alliance community's maturation by 2007: the early conversations about whether Agile methods worked at all had given way to harder questions about why lean transformation attempts stalled at scale, questions that pointed inevitably to leadership and organizational design.