"Lessons in Agile Management: On the Road to Kanban" (2012) is a compilation of blog posts documenting Anderson's intellectual journey from his early work on Theory of Constraints and agile methods (the period covered by agile-management-for-software-engineering) through the development of the kanban-method at corbis and its codification in the kanban-book.
Intellectual autobiography
The book's value is primarily as intellectual autobiography rather than as a systematic exposition of the Kanban Method. It provides a view into how Anderson's thinking evolved — the problems he was trying to solve, the intellectual resources he drew on at each stage, and how ideas from eliyahu-goldratt, don-reinertsen, taiichi-ohno, and w-edwards-deming were incorporated into his thinking over time.
The "road to Kanban" framing signals that the book bridges the pre-kanban-era and the corbis-experiment-era: the posts document the period in which Anderson was working out the ideas that became the Kanban Method, before they had been codified and named.
Blog as intellectual record
The compilation format reflects the role that blog writing played in the Agile and Lean software communities in the mid-2000s. Anderson's blog was a significant venue for developing and testing ideas, engaging with practitioners, and building the community that eventually became the Kanban movement. The posts capture arguments in a form closer to real-time intellectual work than the polished exposition of the kanban-book.
For historians of the Agile and Lean software movements, the compilation is a primary source for the intellectual context in which the Kanban Method emerged — alongside the corbis-kanban-presentation (the first public presentation) and the kanban-book (the systematic codification).
Bridge document
The book bridges the two major phases of Anderson's published work: the pre-Kanban period represented by agile-management-for-software-engineering and the post-Kanban period represented by the kanban-book and subsequent works. It shows the continuity of Anderson's concerns — economic framing, systems thinking, organizational change — across the shift from a TOC-based to a Kanban-based approach.