Work In Progress (WIP) Limits
What you'll learn: How to set and enforce WIP limits per Kanban board column to prevent bottlenecks and maintain smooth workflow.
The Core Idea
WIP limits are constraints placed on each column of your Kanban board that cap how many items can be "in progress" at once. Think of it like a highway: when too many cars try to merge into one lane, traffic slows down. Similarly, when too much work piles up in one stage of your workflow, everything grinds to a halt.
By setting a maximum number (e.g., "Dev in Progress: Max 3"), you force the team to finish existing work before starting new tasks. This reveals bottlenecks quickly—if the "Testing" column is always at its limit while "Development" sits empty, you know where your constraint is.
Why WIP Limits Matter
Without WIP limits, teams often start many tasks simultaneously, context-switching constantly and finishing nothing. WIP limits encourage pulling work through the system rather than pushing more onto overloaded team members. When a column hits its limit, the team must either help clear that stage or wait—both actions expose and address systemic issues.
For example, if your "Code Review" column has a limit of 2 and is full, developers can't push more code. Instead, they might help review existing PRs, immediately addressing the bottleneck rather than letting it grow.
Setting Effective Limits
Start conservatively (often number of team members - 1 per column) and adjust based on flow metrics. Too strict? Work stalls unnecessarily. Too loose? You gain no benefit. The right limit creates healthy tension that drives collaboration without causing paralysis.
Key Takeaway: WIP limits per column prevent multitasking chaos, surface bottlenecks early, and force teams to focus on finishing work rather than starting more—transforming your Kanban board from a status tracker into a flow optimization tool.