Visualize the work
Cards on a board, columns for workflow states (Backlog → In Progress → Blocked → Done is the most common starter setup). You can't manage flow you can't see — the board IS the process visible.
Limit work-in-progress (WIP)
The defining practice. Each column has a cap. New work enters only when capacity opens up. WIP limits force you to finish before you start — a system with too much WIP gets slower, not faster, because each item competes for attention.
Stop starting; start finishing.
— Donald Reinertsen, paraphrased
Manage flow
Track cycle time (how long from In Progress → Done) and look for variance. A long cycle time means work is getting stuck somewhere. A high-variance cycle time means the system is unpredictable — your forecasts won't hold.
Kanban vs. Scrum
| Scrum | Kanban | |
|---|---|---|
| Iteration | Time-boxed sprints | Continuous flow |
| Roles | PO, SM, Devs | None prescribed |
| Commitment | Per sprint | Per pull (when WIP opens) |
| Change in mid-iteration | Discouraged | Allowed |
| Best for | Predictable cadence, customer demos | Continuous-demand, support, ops |
↳ in the wild
The team that adds Kanban without WIP limits has reinvented a to-do list. The team that adds WIP limits without buy-in has a board everyone ignores. The discipline is the limit, not the board.