Work in Progress Limits in PRINCE2 Agile Foundation
Introduction
Work in Progress (WIP) limits are a fundamental concept in PRINCE2 Agile and in agile ways of working more broadly. They are a technique used to improve flow, increase focus, and expose bottlenecks within a team's workflow. Understanding WIP limits is essential for the PRINCE2 Agile Foundation exam, as they represent one of the key mechanisms for delivering value efficiently.
What are Work in Progress Limits?
A Work in Progress limit is a cap on the number of items (such as tasks, user stories, or work packages) that a team allows to be in progress at any one time within a particular stage of their workflow. Rather than starting many tasks at once, the team agrees a maximum number that can be worked on simultaneously.
WIP limits are most commonly associated with Kanban, one of the agile methods that PRINCE2 Agile draws upon. On a Kanban board, columns representing stages of work (for example: To Do, In Progress, Testing, Done) each have a defined WIP limit displayed at the top of the column.
Why are Work in Progress Limits Important?
WIP limits matter because they directly address a common problem in project delivery: starting too many things and finishing too few. Their key benefits include:
1. Improving flow: By limiting how much work is in progress, items move through the workflow more smoothly and are completed faster.
2. Exposing bottlenecks: When a column reaches its limit, work stops flowing, making it visible where blockages occur so the team can address them.
3. Increasing focus: Team members concentrate on finishing existing work before pulling in new work, reducing the inefficiency of multitasking.
4. Encouraging collaboration: When one stage is blocked, team members are prompted to help resolve the bottleneck rather than starting unrelated tasks (this is sometimes called "swarming").
5. Reducing waste: Less unfinished work means less rework, less context switching, and faster delivery of value.
How Do Work in Progress Limits Work?
WIP limits operate on a pull system rather than a push system. Instead of pushing work onto team members, new work is only pulled into a stage when there is capacity available (i.e. when the current WIP is below the limit).
For example, if the "In Progress" column has a WIP limit of 3, the team cannot begin a fourth task until one of the existing three is completed and moved to the next column. This forces the team to finish work before starting new work.
When work becomes blocked, the WIP limit prevents the team from simply moving on and ignoring the problem. Because they cannot start new work, they are motivated to resolve the blockage. Over time, teams may adjust WIP limits based on observation and experimentation to optimise their throughput.
Relationship to Little's Law
WIP limits are underpinned by Little's Law, which describes the relationship between work in progress, throughput, and cycle time. In simple terms, the more items you have in progress, the longer it takes to complete each one. By limiting WIP, teams reduce cycle time and deliver value more predictably.
WIP Limits within PRINCE2 Agile
PRINCE2 Agile blends the governance and control of PRINCE2 with the flexibility of agile. WIP limits support the PRINCE2 focus on delivering products by ensuring work flows efficiently. They complement the concept of managing by stages and controlling work packages, helping teams stay in control of what is being delivered while remaining flexible.
How to Answer Exam Questions on Work in Progress Limits
At Foundation level, questions are typically knowledge-based and may test your understanding of definitions, purposes, and benefits. You should be able to:
- Recognise that WIP limits cap the number of items being worked on at once.
- Identify that WIP limits are associated with Kanban and pull systems.
- Explain the benefits: improving flow, exposing bottlenecks, increasing focus, and reducing multitasking.
- Distinguish WIP limits from other agile techniques such as timeboxing or burn charts.
Exam Tips: Answering Questions on Work in Progress Limits
Tip 1: Remember the core purpose — if a question asks what WIP limits achieve, the safest answers relate to improving flow and exposing bottlenecks.
Tip 2: Associate WIP limits with Kanban and the concept of a pull system. If a question mentions pulling work only when capacity allows, WIP limits are likely the answer.
Tip 3: Watch for distractor answers. WIP limits do not increase the amount of work done at once — they deliberately reduce it. Any option suggesting "doing more tasks simultaneously" is usually wrong.
Tip 4: Connect WIP limits to reducing multitasking and encouraging teams to finish before starting new work.
Tip 5: Read the question carefully to distinguish between related concepts. Timeboxing limits time, whereas WIP limits limit the number of items in progress.
Tip 6: For scenario questions, look for symptoms such as too much unfinished work, hidden bottlenecks, or teams starting many tasks but finishing few — these point to a need for WIP limits.
Summary
Work in Progress limits are a simple yet powerful technique for improving delivery efficiency. By capping the amount of concurrent work, teams complete items faster, reveal bottlenecks, and maintain focus. For the exam, focus on understanding what WIP limits are, their link to Kanban and pull systems, and their key benefits of improving flow and exposing problems.
