"Kanban: An Alternative Path to Agility" (2008) is a conference talk in which Anderson presented the kanban-method as a distinct alternative to prescriptive Agile frameworks, particularly Scrum. Delivered during the community-building-era, the talk positioned Kanban not as a variant of Scrum or an addition to the Agile toolkit but as a fundamentally different approach to achieving agility in software organizations.
The alternative path argument
The talk's framing was deliberate and somewhat provocative: the word "alternative" signaled that Anderson was not arguing for Kanban as a complement to Scrum (a "Scrumban" position that others would later articulate) but as a genuinely different approach. The core contrast was between prescriptive and evolutionary change.
Scrum and other Agile frameworks of the period required organizations to adopt a defined set of roles (Product Owner, Scrum Master, Development Team), ceremonies (Sprint Planning, Daily Standup, Sprint Review, Retrospective), and artifacts (Product Backlog, Sprint Backlog, Increment). These prescriptions were justified as best practices derived from empirical observation, but they required organizations to change their existing processes substantially before any benefit could be measured.
The Kanban approach, Anderson argued, started where the organization was — with its existing workflow, roles, and processes — and used WIP limits and flow visualization as a minimal intervention that would surface problems and create demand for further improvement. This evolutionary approach generated less resistance and was more likely to be sustained than a prescriptive approach that required wholesale process replacement.
Context in Anderson's bibliography
The talk belongs to the period between the corbis-kanban-presentation (June 2007) and the kanban-book (2010) — when Anderson was refining the Kanban Method's conceptual framing and building the community that would eventually form around it. The "alternative path" framing became a persistent thread in Anderson's positioning of the Kanban Method, eventually informing the change management chapters of the kanban-book and the broader evolutionary-change thesis.
The talk also reflects the competitive landscape of the Agile community in 2008, when Scrum had achieved dominance as the default Agile framework and any alternative needed to be positioned explicitly against it. Anderson's argument that Kanban was not merely a different process but a different theory of change — evolutionary rather than prescriptive — was the intellectual foundation for the Kanban Method's subsequent identity.