Work In Progress (WIP)

Work In Progress (WIP) refers to all work items that have been started but are not yet completed. In Agile and Kanban environments, WIP is one of the most important metrics used to measure how much work is currently being handled by a team at any given time.

Managing WIP effectively helps teams improve focus, reduce bottlenecks, increase productivity, and deliver value faster.

---

What Is Work In Progress?

Whenever a team starts working on a task but has not completed it, that task becomes part of the team's WIP.

WIP includes all items that are:

• In Development
• In Testing
• In Review
• Waiting for Approval
• Partially Completed

Completed work items and items that have not yet been started are not considered WIP.

---

Example of Work In Progress

Consider a Scrum Team working on the following user stories:

User Story	Status	WIP?
User Login Feature	In Development	Yes
Shopping Cart Feature	In Testing	Yes
Payment Gateway	To Do	No
Search Feature	Done	No

In this example, the team's WIP count is 2 because two work items are currently in progress.

---

Why WIP Is Important

Many teams mistakenly believe that starting more work means achieving more work. In reality, too much WIP often slows down delivery because team members become overloaded and frequently switch between tasks.

Managing WIP helps teams focus on finishing work before starting new work.

Benefits of Controlling WIP

• Improves team focus.
• Reduces multitasking.
• Speeds up delivery.
• Improves quality.
• Reduces bottlenecks.
• Increases predictability.
• Improves workflow efficiency.

---

Understanding WIP Limits

A WIP Limit is the maximum number of work items allowed in a particular workflow stage at one time.

WIP limits are widely used in Kanban systems to prevent teams from taking on too much work simultaneously.

Example of WIP Limits

Workflow Stage	WIP Limit
Development	5
Testing	3
Code Review	2

If the Development stage already contains 5 tasks, no new work can enter that stage until one of the existing tasks is completed or moved forward.

---

How Too Much WIP Creates Problems

Excessive WIP often leads to slower delivery and reduced efficiency.

Problem	Impact
Multitasking	Reduces focus and productivity.
Context Switching	Increases mental workload.
Longer Cycle Time	Work takes longer to complete.
More Defects	Quality decreases.
Team Stress	Increases burnout risk.
Bottlenecks	Workflow slows down.

---

Low WIP vs High WIP

Low WIP	High WIP
Better focus.	Frequent multitasking.
Faster completion.	Slower delivery.
Higher quality.	More defects.
Shorter Cycle Time.	Longer Cycle Time.
Lower stress.	Higher stress.

---

Relationship Between WIP and Cycle Time

WIP and Cycle Time are closely connected.

Generally:

When teams work on too many items simultaneously, each item takes longer to complete because attention is divided among multiple tasks.

---

Relationship Between WIP and Throughput

Many teams assume increasing WIP increases Throughput. However, the opposite often happens.

Excessive WIP creates bottlenecks that slow down overall delivery.

WIP Level	Expected Throughput
Controlled WIP	Higher Throughput
Excessive WIP	Lower Throughput

---

WIP in Scrum

Although Scrum does not explicitly require WIP limits, Scrum teams often manage WIP to improve sprint performance.

Scrum Masters encourage teams to:

• Finish work before starting new work.
• Avoid excessive multitasking.
• Focus on Sprint Goals.
• Reduce unfinished work at the end of the sprint.

---

WIP in Kanban

WIP limits are a core practice of Kanban.

Kanban teams continuously monitor workflow stages and restrict the number of items that can exist in each stage.

This approach improves flow efficiency and reduces delays.

---

How Scrum Masters Can Reduce WIP

• Encourage completing existing work first.
• Break large stories into smaller stories.
• Identify and remove bottlenecks.
• Use visual boards to track work.
• Promote collaboration among team members.
• Limit multitasking.
• Implement WIP limits where appropriate.

---

Real-World Example

Imagine a team of five developers working on an e-commerce platform.

Initially, each developer starts three stories simultaneously, resulting in 15 active work items. The team experiences delays, frequent context switching, and unfinished work.

The Scrum Master introduces a WIP limit of 5 stories. Team members focus on completing stories before starting new ones.

As a result:

• Cycle Time decreases.
• Throughput increases.
• Quality improves.
• Stress levels decrease.

---

Common Mistakes Related to WIP

Mistake	Result
Starting too many tasks.	Reduced productivity.
Ignoring bottlenecks.	Workflow delays.
No WIP limits.	Work accumulation.
Rewarding task starts instead of completions.	Unfinished work increases.
Excessive multitasking.	Longer delivery times.

---

Key Takeaways

• Work In Progress (WIP) represents work that has started but is not yet completed.
• Managing WIP improves focus, quality, and delivery speed.
• WIP limits help prevent overload and bottlenecks.
• Lower WIP often results in shorter Cycle Time and higher Throughput.
• Both Scrum and Kanban teams benefit from controlling WIP.
• Successful Agile teams focus on finishing work rather than starting more work.

---

Conclusion

Work In Progress (WIP) is a critical Agile metric that helps teams maintain focus, improve workflow efficiency, and deliver value faster. By limiting the amount of active work, teams can reduce multitasking, shorten Cycle Time, increase Throughput, and improve overall product quality. Effective WIP management is one of the key practices used by high-performing Agile teams.