Limiting Work in Progress (WIP) – some anecdotes worth thinking about when using Kanban with Scrum


Co-Creating and teaching the new Professional Scrum with Kanban class has given me an opportunity to get back to geeking out on WIP limits, flow metrics, and all things Kanban. And it’s been fun!

One of the key Kanban practices is Limiting Work in Progress. If you want to be pedantic, actually what this practice aims for is Reducing and stabilizing Work in Progress. This improves flow, provides predictability, and is actually even more important for creating a pull-based Kanban system than visualizing your workflow using a Kanban board. I worked with several clients who limited their WIP but didn’t use Kanban boards. One could argue that maybe this practice deserves to be first in the list of Kanban practices, ahead of Visualization.

Anyhow, when a Scrum Team implements Kanban they should definitely figure out how to limit and reduce their Work in Progress. This is a key part of their definition of “Workflow”. First of all, when we say flow we mean flow of valuable items – so flow of PBIs (rather than tasks).

Now, a question comes up: Who should define the WIP Limit? Let’s assume the team is using Kanban to improve the Sprint flow by visualizing and managing flow in the Sprint Backlog. Sprint Backlog is owned by the Development Team so it would make sense for them to own their workflow and specifically the WIP limits in this case.

What if the team is using Kanban from a more holistic perspective, starting from the Product Backlog and including refinement work as well? In this case, it would be the Scrum Team that would own the workflow and therefore would need to discuss WIP limits.

Now, what if the Dev Team actually wants to involve the Product Owner in their Sprint flow – e.g. to review and accept a story during the Sprint before it goes through testing? Who decides whether to do this? Who owns the Sprint Backlog in this case? I think it is the Scrum Team.

Ok, so we understand who defines workflow and therefore WIP limits. Now let’s assume a team is mid-Sprint and there’s an important valuable item the Product Owner wants to add to the Sprint Backlog. It is aligned with the Sprint Goal. The team is currently at its WIP Limit. Could they add this item? Should they? What needs to happen to the WIP limit?

My take on this is that first of all a decision needs to be made on whether to pull this item into the Sprint Backlog. This discussion isn’t related to Kanban at all. It is a core Scrum question and the answer is that it is up to the team to agree to pull a new item into the Sprint Backlog. The Sprint Goal can be used to assess how aligned this item is with the current focus.

In case the item is pulled into the Sprint Backlog, then the Dev Team needs to figure out whether they can actually start it right away. This depends on the WIP limits and the current WIP. If the team is at their WIP they shouldn’t pull in that new item until some room frees up. If their backlog items are pretty small, an empty WIP slot will free up pretty quickly. If items are big, it can take a while.

The longer it might take to get a normal pull slot ready, the more pressure there might be to actually expedite this card. What is expediting? going beyond the current WIP limits and pushing this item along on top of the existing flow. The typical way to do this is NOT to change the WIP limit definition but to go above WIP and note a WIP exception. These exceptions can then be a topic for inspection and adaptation come time to retrospect.

In general, I don’t recommend changing WIP limits on a whim just because there seems to be a need during the Sprint. I’d rather see an exception and discussion rather than hide the problem under a policy change. Most of the time, Scrum Teams should adjust WIP limits during the Sprint Retrospective out of an attempt to create a better flow strategy, not a way to manage at the tactical level. This is similar to the definition of Done. We don’t change the definition of Done during a sprint just because we have a problem creating a Done Increment. We note the exception, maybe even fail to create a really Done Increment, and we discuss the definition during our Retrospective.

One last thing to note about limiting WIP is that while we typically talk about limiting WIP as per-lane constraints on your workflow, this is actually just one specific way to do it. You could limit the amount of work in progress per person, per the entire team throughout their workflow, or actually, you could limit WIP by time. E.g. “we won’t work on more than 10 items this week”. Hey – that sounds familiar! #SprintForecast.

NOTE: Updated to emphasize that we want to limit WIP by valuable PBIs (rather than tasks). Thanks, Giora for suggesting to make that explicit.

Subscribe for Email Updates:



Agile Mindset
Managing Risk on Agile Projects
Professional Scrum with Kanban
Agile and DevOps Journey
Agile Assembly Architecture
Scrum Values
Risk Management on Agile Projects
Quality Assurance
Principles of Lean-Agile Leadership
Pomodoro Technique
Agile for Embedded Systems
Agile Exercises
Story Slicing
Implementation of Lean and Agile
Nexus Integration Team
ALM Tools
Coaching Agile Teams
speed at scale
Development Value Streams
Entrepreneurial Operating System®
speed @ scale
Scrum and XP
Lean and Agile Techniques
Applying Agile Methodology
Limiting Work in Progress
System Integration Environments
Advanced Roadmaps
Jira Cloud
Agile in the Enterprise
Hybrid Work
Rapid RTC
Agile Product Ownership
Certified SAFe
Agile Games and Exercises
Business Agility
RTE Role
Agile Risk Management
Lean Agile
Engineering Practices
Agile Release Planning
Lean and Agile Principles and Practices
System Archetypes
Kaizen Workshop
Games and Exercises
Agile Community
Managing Projects
Introduction to Test Driven Development
Agile Basics
Agile Delivery
A Kanban System for Software Engineering
Agile Games
Change Management
Continuous Integration
What Is Kanban
Risk-aware Product Development
Implementing SAFe
Acceptance Test-Driven Development
System Team
Portfolio for Jira
Continuous Planning
An Appreciative Retrospective
Lean Agile Basics
Agile Israel Events
Lean Agile Organization
Agile Testing Practices
PI Objectives
Product Ownership
Agile India
Scrum With Kanban
PI Planning
Professional Scrum Master
Lean Startup
Lean Budgeting
Agile Israel
Agile Project Management
Lean Software Development
Scrum Guide
Kanban Basics
Scrum Master Role
Product Management
The Kanban Method
Sprint Planning
SAFe Release Planning
Scaled Agile Framework
Agile Contracts Best Practices
ART Success
Artificial Intelligence
Kanban Kickstart Example
Test Driven Development
Program Increment
Professional Scrum Product Owner
Lean-Agile Software Development
Agile Outsourcing
Introduction to ATDD
Accelerate Value Delivery At Scale
Agile Project
Jira admin
Reading List
Releases Using Lean
AI Artificial Intelligence
Continuous Deployment
SAFe DevOps
Daily Scrum
Sprint Retrospectives
Sprint Iteration
IT Operations
Nexus and SAFe
Value Streams
Manage Budget Creation
Lean Risk Management
Achieve Business Agility
Scrum Master
Continuous Delivery
Lean-Agile Budgeting
Jira Plans
lean agile change management
Legacy Code
Agile Techniques
Nexus and Kanban
Software Development
Agile Development
Built-In Quality
Lean Agile Leadership
Process Improvement
Continuous Improvement
Effective Agile Retrospectives
Scrum Primer
Release Train Engineer
Agile Program
Agile Product Development
ScrumMaster Tales
Lean Agile Management
Agile Release Management
Kanban 101
Elastic Leadership
Software Development Estimation
The Agile Coach
Agile Marketing
Legacy Enterprise
Iterative Incremental Development
Enterprise DevOps
Kanban Game
Perfection Game
Large Scale Scrum
Operational Value Stream
Risk Management in Kanban
Systems Thinking
Enable registration in settings - general

Contact Us

Request for additional information and prices

AgileSparks Newsletter

Subscribe to our newsletter, and stay updated on the latest Agile news and events

This website uses Cookies to provide a better experience
Shopping cart