Handling WIP Limit Violations

When a WIP limit is reached, you have three options:

1. Wait — Don't start new work; help finish something in progress
2. Swarm — Multiple people help clear the bottleneck
3. Violate — Start new work anyway, acknowledging the exception

All three are valid depending on context. The key is that the violation is visible and conscious, not invisible and unconscious.

A violated limit is a signal: "Something unusual is happening. Pay attention."

Step 1: Recognize the signal The limit is hit. This is the system working, not breaking.

Step 2: Ask why

• Is there a blockers preventing work from finishing?
• Is a downstream stage backed up?
• Did we take on too much work?
• Is something unexpectedly complex?

Step 3: Choose a response

• Help finish something: Review a PR, pair on a bug, clear a blocker
• Swarm on the bottleneck: Multiple people focus on clearing the jam
• Wait: If the blocker is external, there may be nothing to do but wait
• Escalate: If the pattern persists, raise it in standup or to leadership

Step 4: Don't automatically violate The temptation is to say "but this is important!" and start anyway. Resist. The limits exist to protect flow.

Sometimes violating the limit is the right call. Examples:

Genuine emergency: Production is down, and we're at WIP limit for Dev. Yes, start the fix anyway.

Blocking dependency: The blocked item is waiting on external input. Starting something else is better than sitting idle.

Learning: New team member needs to pair, and that temporarily exceeds limit.

But make it visible:

• Use a visual indicator (different color card, flag, etc.)
• Discuss in standup
• Track violations over time

If you're violating limits frequently, something is wrong. Either:

• Limits are too low
• Work is coming in too fast
• Blockers aren't being resolved
• The team doesn't believe in the limits

Violations are data. Track them to improve:

What to capture:

• When did the violation happen?
• Why was the limit hit? (blocker, upstream surge, etc.)
• Why did we choose to violate? (emergency, couldn't help elsewhere, etc.)
• What was the impact?

Patterns to look for:

• Same column always hitting limits → bottleneck, address root cause
• Limits hit after replenishment → taking on too much in planning
• Violations always from one person → possible training or support need
• Violations always for one work type → maybe that type needs different handling

Retro discussion: "We violated the Dev WIP limit 4 times this sprint. Three were because Code Review was backed up. Do we need to increase Review capacity?"

This turns violations into improvement opportunities instead of guilt.