"Kanban: Successful Evolutionary Change for Your Technology Business" (2010) is the foundational text of the Kanban Method and Anderson's most consequential work. Published by blue-hole-press with a foreword by don-reinertsen, the book synthesized ideas from four distinct intellectual traditions — Toyota's production system (taiichi-ohno), don-reinertsen's queueing theory, eliyahu-goldratt's Theory of Constraints, and w-edwards-deming's quality management — into a unified change management approach for knowledge work. It has sold over 40,000 copies in eight languages and ranks among the top five best-selling Agile books.
Intellectual synthesis
The Kanban book's central achievement is reframing a production scheduling tool (Toyota's kanban cards) as a mechanism for organizational change. Anderson did not propose that software teams use physical kanban cards to schedule work in the Toyota sense; he proposed that the constraints embodied in a WIP-limited pull system — wip-limits, visualize-workflow, manage-flow — could function as levers for surfacing and resolving systemic problems in knowledge work organizations.
The intellectual sources are explicit throughout. From taiichi-ohno and the Toyota Production System, Anderson took the concepts of pull systems, waste identification (muda), and the practice of making work visible. From don-reinertsen's "Principles of Product Development Flow," Anderson took queueing theory's analysis of WIP, utilization, and the economic cost of delay — particularly the insight that high utilization rates in queuing systems produce disproportionate lead time inflation. From eliyahu-goldratt's Theory of Constraints (which Anderson had already engaged in agile-management-for-software-engineering), he took the focus on bottlenecks, throughput, and the five focusing steps. From w-edwards-deming, he took the emphasis on systemic causes of quality problems and the PDCA improvement cycle.
The six core practices
The book articulates six core practices of the Kanban Method: visualize-workflow, limit WIP, manage-flow, make-policies-explicit, implement-feedback-loops, and improve-collaboratively. These are presented not as a prescribed process but as properties that a well-functioning Kanban system exhibits — a distinction that matters for Anderson's claim that Kanban is an evolutionary rather than revolutionary change approach.
Evolutionary change thesis
The book's most original contribution is its change management framing. Anderson argued that the failure of prescriptive Agile frameworks in large organizations was partly a function of the change approach: asking teams to discard existing processes and adopt a new methodology wholesale (as Scrum and XP require) generates organizational resistance and destabilizes functioning processes. The Kanban Method, by contrast, starts with the team's existing workflow and introduces WIP limits and flow metrics as an overlay — changes small enough to gain acceptance but sufficient to surface dysfunction that then motivates further improvement.
classes-of-service — the categorization of work items by their cost-of-delay profiles (expedite, fixed-date, standard, intangible) — appear in this book as a concrete mechanism for making scheduling policies explicit and managing the flow of heterogeneous work types through a pull system.
Reception and influence
The foreword by don-reinertsen signaled the book's intellectual lineage and helped position it within the product development flow community as well as the Agile community. The book's success established lean-kanban-inc as a training and certification organization and launched a community of practice that eventually became kanban-university.
The Kanban book built directly on the intellectual groundwork of agile-management-for-software-engineering and on Anderson's empirical work at corbis documented in the corbis-kanban-experiment event. The corbis-kanban-presentation at Reinertsen's 2007 conference was the first public presentation of the ideas that became the book.