In 30 seconds
- Stop starting, start finishing.
- Less work in progress means shorter lead time.
- A full column is a signal to help, not to start more.
Why limiting work helps
Little's Law, from queueing theory, says average lead time equals average work in progress divided by average throughput. If throughput stays the same, cutting work in progress cuts how long each item takes. Fewer parallel tasks also means less context switching.
Setting limits
- Start with roughly the number of people working in each column
- Lower limits gradually until flow improves
- Write limits on the board column headers
- Treat a breached limit as a conversation, not a crime
When a column is full
Don't start new work. Help finish what's stuck: review code, test, unblock. This is how WIP limits turn Kanban from a board into a flow system.
Myth vs reality
Myth · WIP limits make people idle.
Reality · Idle people help finish work, which is the point.
Myth · Higher utilization means faster delivery.
Reality · Fully loaded systems slow down sharply.
Myth · Limits never change.
Reality · Adjust them as the team learns.
FAQ
Do Scrum teams need WIP limits?
They're optional but often help within a sprint.
What if urgent work arrives?
Use an expedite lane with its own small limit.
Should individuals have WIP limits?
Many teams set a personal limit of one or two items.