WIP Limits (Work In Progress Limits)

WIP Limits stand for Work In Progress Limits. They are one of the core practices of the Kanban Method and are used to control the amount of work that can be actively worked on at any given time.

By limiting the number of tasks in progress, teams can focus on completing existing work before starting new work. This reduces multitasking, improves workflow efficiency, and helps identify bottlenecks quickly.

---

What Does Work In Progress (WIP) Mean?

Work In Progress refers to all tasks, stories, bugs, features, or work items that have been started but are not yet completed.

Examples of WIP include:

• User stories currently being developed.
• Bugs being fixed.
• Features under testing.
• Tasks waiting for review.

---

Why Are WIP Limits Important?

Without limits, team members often start too many tasks simultaneously. This creates bottlenecks, increases context switching, and slows overall delivery.

WIP Limits encourage teams to finish work before starting new work.

Without WIP Limits	With WIP Limits
Too many tasks started.	Focus on completing tasks.
Frequent multitasking.	Improved concentration.
Hidden bottlenecks.	Bottlenecks become visible.
Long delivery times.	Faster workflow.
Unpredictable results.	More predictable delivery.

---

Understanding WIP Limits with an Example

Consider the following Kanban Board:

+-----------+----------------+------------+--------+
| To Do     | In Progress(3) | Testing(2) | Done   |
+-----------+----------------+------------+--------+
| Story 1   | Story 5        | Story 8    | Story 9|
| Story 2   | Story 6        | Story 10   |        |
| Story 3   | Story 7        |            |        |
| Story 4   |                |            |        |
+-----------+----------------+------------+--------+

The number inside parentheses represents the WIP Limit.

• In Progress can contain a maximum of 3 items.
• Testing can contain a maximum of 2 items.

No additional work can enter a column once its WIP Limit has been reached.

---

How WIP Limits Work

When a workflow stage reaches its maximum capacity:

• No new work can be added.
• Team members must help move existing work forward.
• Bottlenecks become immediately visible.
• Focus shifts from starting work to finishing work.

---

Example Without WIP Limits

Imagine a team of 5 developers working on 20 tasks simultaneously.

Problem	Impact
Frequent task switching	Reduced productivity.
Large number of unfinished tasks	Delayed delivery.
Overloaded testing phase	Quality issues.
Hidden bottlenecks	Slow workflow.

---

Example With WIP Limits

The same team limits active development work to 5 tasks.

Benefit	Result
Less multitasking	Better focus.
Faster completion	Shorter cycle times.
Balanced workload	Improved efficiency.
Visible bottlenecks	Quicker problem resolution.

---

Benefits of WIP Limits

Benefit	Description
Improved Focus	Teams work on fewer items at a time.
Reduced Multitasking	Less context switching.
Faster Delivery	Work reaches completion sooner.
Better Quality	More attention given to each task.
Visible Bottlenecks	Workflow issues become obvious.
Predictable Workflow	Delivery becomes more consistent.

---

How WIP Limits Expose Bottlenecks

Suppose the Testing column has a WIP Limit of 2.

If both testing slots are occupied and developers continue completing work, new tasks cannot enter Testing.

This creates a visible queue and immediately reveals that Testing has become a bottleneck.

Development → Testing (Full) → Done

Cannot move work forward
↓
Bottleneck Detected

---

Determining Appropriate WIP Limits

There is no universal formula for setting WIP Limits. Teams typically start with simple limits and adjust based on experience.

Team Size	Suggested Initial WIP Limit
3 Team Members	2-3 Items
5 Team Members	4-5 Items
8 Team Members	6-8 Items

Teams should continuously review and refine WIP Limits as workflows evolve.

---

Types of WIP Limits

1. Column WIP Limits

Restrict the total number of items allowed in a workflow stage.

Example:

Development (5)
Testing (3)
Review (2)

---

2. Individual WIP Limits

Restrict how many tasks an individual team member can work on simultaneously.

Example:

Developer A → Maximum 2 Tasks
Developer B → Maximum 2 Tasks

---

3. Team WIP Limits

Restrict the total amount of active work across the entire team.

Example:

Entire Team → Maximum 10 Active Items

---

WIP Limits and Agile Metrics

Proper WIP management improves several Agile metrics.

Metric	Impact of WIP Limits
Cycle Time	Usually decreases.
Lead Time	Often improves.
Throughput	May increase.
Predictability	Improves significantly.

---

Common Mistakes When Using WIP Limits

Mistake	Why It Is a Problem
Ignoring WIP limits.	Eliminates the benefits of flow control.
Setting limits too high.	Bottlenecks remain hidden.
Setting limits too low.	Work may become unnecessarily restricted.
Not reviewing limits.	Limits may become outdated.

---

Real-World Example

A software development team notices that completed features are waiting several days for testing. They introduce a WIP Limit of 3 in the Development column. Once the limit is reached, developers assist testers instead of starting new features.

As a result, testing delays decrease, cycle time improves, and overall delivery becomes more predictable.

---

Key Takeaways

• WIP stands for Work In Progress.
• WIP Limits control how much work can be active at one time.
• They reduce multitasking and improve focus.
• WIP Limits help identify bottlenecks quickly.
• They improve workflow predictability and delivery speed.
• Kanban relies heavily on WIP Limits to optimize flow.

---

Conclusion

WIP Limits are one of the most powerful tools in Kanban and Lean practices. By limiting the amount of active work, teams can focus on finishing tasks, reduce bottlenecks, improve collaboration, and deliver value more efficiently. Organizations that effectively use WIP Limits often experience faster delivery, higher quality, and greater predictability in their workflows.