Course contentsShow
← Software Engineering
Lesson 1597 of 1,93346. Agile MethodologiesFree lesson

Identifying and Resolving Bottlenecks

Using WIP limits and flow metrics to spot where work accumulates and taking corrective action.

Identifying and Resolving Bottlenecks

You'll learn how to use WIP limits and flow metrics to pinpoint where work gets stuck and how to take action to clear those blockages.

In Kanban (and Agile in general), a bottleneck is any stage in your workflow where work piles up faster than it can be completed. Think of it like a highway merging from three lanes into one—cars accumulate at that point, slowing everything down.

Spotting Bottlenecks with Flow Metrics

You already know about WIP limits and cycle time. Now use them as diagnostic tools:

  • High WIP in one column: If "In Review" consistently hits its WIP limit while "Development" is empty, reviews are your bottleneck.
  • Increasing cycle time: If tasks suddenly take longer to complete, measure time spent in each stage. The stage with growing wait times is likely your constraint.
  • Work aging: Tasks sitting idle in one column for days signal a blockage.

Resolving Bottlenecks

Once identified, take corrective action:

  1. Redistribute capacity: Move team members temporarily to help clear the backed-up stage (e.g., developers helping with code reviews).
  2. Lower upstream WIP limits: Prevent new work from entering until the bottleneck clears—starving upstream stages is better than clogging the whole system.
  3. Address systemic issues: If testing is always slow, invest in test automation or additional tooling.
  4. Swarm the constraint: Multiple team members collaborate to clear the highest-priority blocked item first.

Think of your workflow like water flowing through pipes—find the narrowest pipe and either widen it or reduce the water pressure feeding into it.

Key Takeaway: Use WIP limits and flow metrics to identify where work accumulates, then take targeted action—redistributing people, limiting upstream work, or fixing systemic issues—to restore smooth flow through your delivery pipeline.