My thoughts on how Kanban and TOC Critical Chain relate
How Kanban and Theory of Constraints Critical Chain overlap and complement each other — both address bottlenecks and WIP, but from different angles. A practitioner comparison.
How Kanban and Theory of Constraints Critical Chain overlap and complement each other — both address bottlenecks and WIP, but from different angles. A practitioner comparison.
How do you scale Kanban beyond a single team? A practical look at fractal flow patterns, explicit policies, and what changes at the portfolio level.
Revisiting my 2011 Lean Kanban Benelux talk on commitments, flow energy, routing, and predictability, with practical guidance for today's product and portfolio environments.
How flow-based approaches reduce testing bottlenecks and stabilization costs — using WIP limits, "done is done" standards, and systematic bottleneck elevation to deliver release-quality software predictably.
How to reduce WIP in brownfield/legacy systems that already have high in-flight work — practical patterns including the freeze, no-new-work, and limit-later approaches.
Impressions from the Lean Software and Systems Conference 2011 — sessions on flow, complexity, Kanban metrics, and the future of lean thinking in software.