Implementing Lean Software Development: From Concept to Cash (2006) is the second book by mary-poppendieck and tom-poppendieck, published by addison-wesley three years after their foundational lean-software-development-agile-toolkit-2003. Where the first book translated TPS principles into software equivalents and named the seven-lean-principles, this volume asked the harder question: how do you actually put lean into practice in real organizations with existing codebases, processes, and cultures?
Subtitle as Thesis
The subtitle "From Concept to Cash" signals the book's framing: value in software flows from concept (customer need identified) to cash (working capability delivered). The lean task is to compress that cycle — not by working faster in isolated steps, but by identifying and eliminating the delays, handoffs, and queues that accumulate between steps. This framing connected lean software directly to the lean manufacturing value stream concept and set up the book's central analytical tool.
Value Stream Mapping for Software
The most significant contribution of the 2006 book is the introduction of value-stream-mapping-for-software as a practical diagnostic technique. Borrowed from Learning to See (Rother and Shook, 1998) in the manufacturing tradition, value stream mapping traces the flow of value from customer request to delivery, marking each step with lead time and process time to identify where waiting, rework, and waste accumulate.
mary-poppendieck's insight was that software development has a value stream that can be mapped, even though the "product" is information rather than physical material. The map typically reveals that process time (actual work) is a small fraction of lead time (total elapsed time), with the remainder consumed by queues, approvals, handoffs, and waiting. This is not a new problem — taiichi-ohno identified the same pattern in manufacturing — but making it visible in software required adapting the technique to information flows.
Pull Systems and Queueing Theory
The 2006 book deepened the treatment of pull-systems-in-software, moving beyond the principle-level introduction in lean-software-development-agile-toolkit-2003 to the mechanics of implementing pull in development workflows. This is where mary-poppendieck and tom-poppendieck engaged most directly with donald-reinertsen's work on product development flow and queueing theory.
donald-reinertsen's queueing theory analysis — showing that queue length, variability, and utilization interact in non-linear ways, and that high utilization rates produce disproportionate queue growth — is cited extensively. The implication for software teams is that running teams at or near 100% capacity does not maximize throughput; it maximizes queue length and delays. Building slack into the system is not waste — it is the condition that enables pull to function. This was a counterintuitive finding that the Poppendiecks presented with mathematical grounding.
Case Studies and Implementation Depth
Unlike lean-software-development-agile-toolkit-2003, which was organized around principles with illustrative examples, Implementing Lean Software Development included more detailed case studies of real organizations applying lean practices. These case studies served the book's practical mandate: to give teams not just principles but enough implementation detail to begin their own lean transformation.
The case studies also documented failure modes — what happens when organizations adopt lean vocabulary without lean thinking, when teams optimize locally rather than at the system level (violating optimize-the-whole), and when lean is treated as a toolkit of practices rather than a set of principles requiring judgment.
Relationship to Adjacent Thinking
The 2006 book positioned lean software explicitly in relation to:
Significance in the Trilogy
Implementing Lean Software Development occupies the middle position in the Poppendiecks' three-book argument. The first book asked: what are the principles? The second asked: how do you implement them? The third, leading-lean-software-development-2009, asked: what organizational and leadership conditions are required for implementation to succeed at scale? The 2006 book is essential for practitioners who have absorbed the principles and need to translate them into specific process changes — particularly the value stream mapping methodology, which remains one of the most practical diagnostic tools the lean software tradition has produced.