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

Facebook
Twitter
LinkedIn
Pinterest
WhatsApp

Co-Creating and teaching the new Scrum.org 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:

Categories:

Tags:

Rovo
TDD
Keith Sawyer
Continuous Planning
Agile Techniques
Confluence
WIP
Artificial Intelligence
Implementation of Lean and Agile
Video
Kanban 101
Agile Mindset
ATDD
Releases Using Lean
Agile Israel
System Team
Agile Project
Achieve Business Agility
Lean Agile Management
Self-organization
Portfolio for Jira
An Appreciative Retrospective
Kanban
ROI
DevOps
Agile Games
Acceptance Test-Driven Development
Professional Scrum Master
SAFe Release Planning
Continuous Improvement
Agile Community
User stories
GanttBan
Program Increment
Agile Delivery
Kanban Basics
Advanced Roadmaps
IT Operations
Elastic Leadership
Agile Marketing
Kaizen
Scrum Primer
Reading List
Hybrid Work
Lean Startup
Accelerate Value Delivery At Scale
Nexus and SAFe
Business Agility
Presentation
Agile Basics
Coaching Agile Teams
Scrum Master Role
Change Management
Systems Thinking
Kanban Game
AI Artificial Intelligence
Managing Projects
Agile Assembly Architecture
Agile and DevOps Journey
Lean Risk Management
Agile for Embedded Systems
Slides
Principles of Lean-Agile Leadership
ATDD vs. BDD
SA
Continuous Integration
ARTs
ALM Tools
Implementing SAFe
Large Scale Scrum
Quality Assurance
Operational Value Stream
Webinar
Product Ownership
Agile Testing Practices
Software Development
Lean-Agile Software Development
predictability
lean agile change management
Engineering Practices
Agile Product Development
Scrum.org
Introduction to Test Driven Development
Kanban Kickstart Example
PI Objectives
Lean Budgeting
Lean and Agile Principles and Practices
Scrum Guide
Scrum
Agile Release Management
Jira
EOS®
Risk Management on Agile Projects
Pomodoro Technique
Scaled Agile Framework
Agile Program
AI
Atlassian
Story Slicing
Lean and Agile Techniques
LAB
Sprint Iteration
Spotify
The Agile Coach
A Kanban System for Software Engineering
RTE Role
Entrepreneurial Operating System®
Daily Scrum
Continuous Deployment
Continuous Delivery
Agile Exercises
PI Planning
Lean Agile
BDD
Lean Agile Leadership
System Archetypes
Software Development Estimation
Legacy Enterprise
ART Success
The Kanban Method
RSA
ScrumMaster Tales
Jira Cloud
POPM
Applying Agile Methodology
Agile Product Ownership
SAFe
Sprint Planning
Tools
Agile India
AgileSparks
System Integration Environments
Lean Agile Organization
Frameworks
Jira admin
Professional Scrum with Kanban
Agile Games and Exercises
Effective Agile Retrospectives
What Is Kanban
SPC
Nexus
Manage Budget Creation
Retrospectives
Nexus Integration Team
LPM
Agile
Agile Development
Professional Scrum Product Owner
Legacy Code
Atlaassian
Test Driven Development
speed at scale
Agile in the Enterprise
Introduction to ATDD
Agile Release Planning
Agile Israel Events
Nexus vs SAFe
Agile Contracts Best Practices
Agility
Release Train Engineer
Scrum Values
QA
Lean Software Development
Product Management
speed @ scale
Enterprise DevOps
Built-In Quality
LeSS
Scrum Master
Amdocs
agileisrael
Lean Agile Basics
transformation
Iterative Incremental Development
Process Improvement
NIT
Risk Management in Kanban
Covid19
Managing Risk on Agile Projects
Rapid RTC
Agile Project Management
Games and Exercises
Risk-aware Product Development
Development Value Streams
chatgpt
RTE
Lean-Agile Budgeting
Scrum and XP
Nexus and Kanban
Agile Risk Management
Scrum With Kanban
Perfection Game
Planning
Agile Outsourcing
Value Streams
Sprint Retrospectives
Code
SAFe DevOps
Team Flow
Certified SAFe
Tips
Certification
Kaizen Workshop
Jira Plans
AgileSparks
Logo
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