Skip to content
PMPCAPM

Work in Progress (WIP) Limits

Work in Progress (WIP) Limits are constraints placed on the number of work items allowed in each stage of a workflow at any given time, designed to improve flow and reduce multitasking.

Share:

Know it well enough for the exam? Questions on Work in Progress (WIP) Limits are scenario-based, not definitional.

Practice it free

Explanation

WIP limits are a core Kanban practice that prevent teams from overloading any stage of their workflow. By limiting the number of items in progress at each column on the Kanban board, teams focus on completing work rather than starting new work. This reduces context switching, reveals bottlenecks, and improves overall throughput.

When a WIP limit is reached, the team cannot pull new work into that stage until an existing item moves forward. This forces the team to address whatever is blocking progress, whether it is a dependency, a skills gap, or a capacity issue. Over time, this focus on flow leads to shorter cycle times and more predictable delivery.

Setting the right WIP limits requires experimentation. If limits are too high, they have no effect. If too low, they may starve downstream stages. Teams typically start with a limit roughly equal to the number of people working at that stage, then adjust based on data and retrospective discussions.

Key Points

  • •Limit the number of items in each workflow stage
  • •Reduce multitasking and improve focus on completing work
  • •Reveal bottlenecks by forcing the team to address blocked items
  • •Should be adjusted over time based on data and team experience

Exam Tip

WIP limits help improve flow and reduce cycle time. If a question describes a team with many items started but few completed, introducing WIP limits is the best answer.

Frequently Asked Questions

Related Topics

High-yield topics our learners drill most before exam day.

Burndown Chart

A burndown chart plots the work remaining (usually in story points) against time in a sprint or release, alongside an ideal line to zero, so the team can see each day whether it is on track to finish.

Burn-Up Chart

A burn-up chart plots completed work rising over time against a separate total-scope line, so progress and scope changes are visible independently; the work is finished when the two lines meet.

Weighted Shortest Job First (WSJF)

Weighted Shortest Job First (WSJF) is a prioritization model, popularized by SAFe, that ranks work by cost of delay divided by job duration (usually estimated as job size), so the items that lose the most value per unit of time spent waiting are done first.

Relative Estimation

Relative Estimation is an agile technique where work items are sized in comparison to each other rather than in absolute units like hours or days, providing faster and more accurate estimates.

Sprint Review

The Sprint Review is a Scrum event held at the end of the Sprint where the Scrum Team presents the Increment to stakeholders, gathers feedback, and collaborates on what to do next.

Sprint Backlog

The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus the Sprint Goal and the plan for delivering the Increment.

Timeboxing

Timeboxing is the practice of allocating a fixed, maximum amount of time for an activity, after which the activity stops regardless of whether it is complete.

Resource Leveling

Resource leveling is a resource optimization technique that adjusts activity start and finish dates so that demand for a resource never exceeds its availability, accepting a longer schedule and a changed critical path if necessary.

Deliverables

A deliverable is any unique and verifiable product, result, or capability to perform a service that must be produced to complete a process, phase, or project, such as a software release, an audit report, or a trained support team.

Part of

Agile & Hybrid

Study full domain →

Practice Work in Progress (WIP) Limits

Scenario-based questions with a full explanation on every answer — including why the distractors are wrong.