David Anderson developed the Kanban method for software and knowledge work teams, creating an operational framework that made the Poppendiecks' lean software principles tangible through visual boards, explicit WIP policies, and measured flow metrics.
From lean software to Kanban
Anderson's Kanban method draws directly on mary-poppendieck and tom-poppendieck's work on pull-systems-in-software, WIP limits, and flow. The Poppendiecks had established the principled case: eliminate-waste through limiting work-in-process, deliver-as-fast-as-possible through small batches and pull, optimize-the-whole by measuring end-to-end cycle time rather than individual utilization. Anderson's contribution was making these principles operational through a specific visual management system that teams could implement without abandoning their existing process.
WIP limits and flow
The defining mechanism of Anderson's Kanban method is the explicit WIP limit — a cap on how much work can be in each stage of a workflow at any time. This operationalizes the queueing theory logic that donald-reinertsen had formalized and that the Poppendiecks had applied to software: high utilization creates queues, queues create delay, delay destroys value. By making WIP visible and constrained, Kanban teams surface bottlenecks and create the conditions for deliver-as-fast-as-possible.
Connection to taiichi-ohno
Anderson's Kanban method also draws on taiichi-ohno's original kanban card system from Toyota's factories — the visual signal that authorizes production only when downstream capacity exists. Anderson adapted this pull logic for software team workflows, creating a lineage that runs from Toyota production to lean manufacturing to the Poppendiecks' lean software framework to Kanban for knowledge work.
Lean Kanban University
Anderson founded Lean Kanban University to certify Kanban practitioners and extend the method across industries. This institutional work extended the reach of lean software principles — including the Poppendiecks' seven-lean-principles — into organizations that might not have engaged with lean manufacturing origins directly.