Kanban WIP Limits

Work in Progress limits, often shortened to WIP limits, control how many tasks can sit in a column at the same time. This single rule shapes how a Kanban team operates every day.

What a WIP Limit Looks Like

A column displays its WIP limit next to its name, such as "In Progress (3)". This means only three tasks may occupy that column at once.

In Progress (WIP limit: 3)
   Task A
   Task B
   Task C
   Task D -> BLOCKED, must wait

Task D cannot enter the column until one of the three existing tasks moves forward to the next stage.

Why WIP Limits Matter

People often believe working on many tasks at once gets more done. In reality, switching between tasks wastes time and increases mistakes. WIP limits force team members to finish current work before starting something new.

Revealing Bottlenecks

A column that constantly hits its WIP limit signals a bottleneck. The team can see exactly where work piles up and investigate the cause, such as a missing reviewer or a slow approval step.

Backlog | To Do | In Progress (3/3) | Review (1/2) | Done
        |       | FULL - blocked    |              |

Setting the Right Limit

Teams often start with a WIP limit close to the number of people working in that stage. A column handled by three developers might start with a WIP limit of three or four. Teams adjust the number up or down after observing how work flows over a few weeks.

Layman's Example

Think of a single-lane car wash. Only one car can sit inside the wash bay at a time. A line of waiting cars outside does not mean the wash works faster. The limit on cars inside the bay keeps the process organized and prevents collisions.

Key Takeaway

WIP limits stop teams from juggling too many tasks at once. They expose bottlenecks quickly and push the team to finish existing work before starting anything new.