Kanban WIP Limits: Choosing Numbers That Actually Hold

Work in Progress (WIP) limits are not dogma; they are boundaries built from experience. While the purest Agile theory suggests setting a limit, picking the right number for your remote team—one that genuinely reflects capacity rather than just aspiration—is an art form. Setting limits too high just encourages distributed chaos across time zones.

Determining the perfect number requires empirical data, not guesswork. Start by mapping genuine cycle time. For instance, if historical data shows developers consistently need 16 hours to fully test a moderately sized feature, assigning them a WIP limit of five items is likely impossible; they will become overloaded juggling context switches. A more realistic ceiling might be three items, compelling the team to swarm and finish what is already started.

When your limit is reached, adapt your process rather than just complaining about the blockage. Have 'swarming' become a recognised ritual. Instead of having three people vaguely "working on" a dependency, assign two people to pair up and focus solely on clearing that one specific card until it moves to 'Ready for Review'.

Avoid the common trap of setting WIP limits based on team size—that correlation rarely holds true in practice. Instead, base it on flow or silos. If 'Design Sign-off' is the bottleneck, place the WIP limit there temporarily, forcing the upstream team (like development) to slow down and focus on supporting the bottleneck process, optimising overall throughput across the distributed organisation.

Takeaways

• Data over Theory: Anchor WIP limits to measured cycle times, not ideal states.
• Embrace Swarming: When the limit is hit, focus effort. Two people finishing one high-priority item is better than five people starting five new ones.
• Silo Limits: Apply the tightest, most accurate limits to the proven chokepoints (e.g., QA Review, Security Architecture).
• Remote Focus: Explicitly schedule 'WIP review' time in stand-ups to acknowledge bottlenecks before they derail the day.

Resources

• Optimising Jira Kanban Boards for Agile Teams: Understanding workflow stages and capacity constraints.
• Understanding Kanban Flow: Reviewing core concepts on flow efficiency theory.