Setting Initial WIP Limits
Starting Point: Team Size as Initial Upper Bound If team size = 5: A reasonable initial WIP cap is: WIP […]
Starting Point: Team Size as Initial Upper Bound If team size = 5: A reasonable initial WIP cap is: WIP […]
When a work item starts to age beyond expectation, teams often face a practical question: Should we move it to
QA as a Separate Workflow State Breaks Flow Many teams still model testing as a distinct workflow state. Work moves
What an Aging Breach Is Really Telling You In Kanban systems, aging is often misunderstood. Teams notice work items getting
One of the most common misunderstandings about Kanban is that it is a way of doing the work. It isn’t.
Kanban is often explained as a collection of practices: Visualize work.Limit WIP.Manage flow.Improve continuously. All of these are correct.None of
Flow-based agility (e.g., Kanban) and timeboxed agility (e.g., Scrum) represent two distinct approaches to managing work. The primary difference lies
Lean Principles Revisited: Why Kanban Is a Control System Lean principles are widely taught, widely cited, and widely misunderstood—especially in
Why Stop Starting Is So Hard If there is one behavior that undermines flow more than any other, it is
One of the most persistent misunderstandings about Kanban is the belief that it is primarily a visualization technique. Boards. Columns.
Many organizations say they are “doing Kanban.”They have boards. They have columns. They move cards. And yet, nothing actually changes.
Kanban as a Process Control System Flow-based management can be understood most clearly by borrowing a concept from control theory.
The Role of Cadence (Still Essential) Cadence does not disappear in a flow-based governance model. Regular, predictable cadence is intentionally
Why We Only Talk About Aging Work For years, I facilitated daily standups that looked like most others:round-robin updates, status
What Does “Pulling Work Continuously” Actually Look Like? In my previous article, I argued that when an organization has a
To unlock the full power of Kanban, teams must move beyond treating it as just a visual task board. By implementing WIP limits, tracking flow metrics, making policies explicit, improving flow, and focusing on continuous improvement.
WIP limits are the key to establishing and optimizing the flow of work in a system. When WIP limits are
Our goal is to deliver maximum value at minimum cost. We seek to achieve this via a relentless focus on
Summary The basic measures of flow are: Cycle Time: The elapsed time between when an item starts and when it
The Kanban Method can be applied as flow accelerator for software delivery frameworks. Adopting the Kanban Method for software development creates efficient and predictable flow of value.