Close this search box.
Close this search box.
Close this search box.

Patterns for getting to a lower WIP level in a system


The Freeze, No New Work, Limit Later, and some Mashups...

Some of us have the luxury of designing processes for greenfield systems meaning there is no history/legacy to deal with.

Typically though, we are dealing with Brownfield/Legacy systems – This usually means there is some work in the system already, there are outstanding commitments, and some existing queues between steps in our processes.

I’m working with several clients that decided to start using a Kanban system to manage their work, and believe Limited Work in Process is key to improving their performance.

But a challenge most of them share is how to deal with is something along the lines of:

  • We already have a commitment to deliver V10 with 20 features by end of October.
  • Our testing department is backlogged – its still dealing with the previous release V9 while development is already working on those 20 features for V10.
  • V10 is critical to the business.

We then discuss various ways to get from here to there.

The Freeze

Essentially prioritize all work. Anything that is in process but above the WIP limit, goes to the freezer – a new temporary lane/area where work is put on freeze until there is room for it.

The immediate effect would be an acceleration of all work inside the WIP limit, and significant risk to the commitment made about the frozen work. Yes, you say that the original commitment took all the work into account so why is there a risk just due to changes in parallelism? Well, because we focus on the higher priority work, the reality is that we might spend more effort on it, to deliver it with reasonable quality (not necessarily an attribute of previous releases…), we might spend more time investing in Versatility in order to sustain a lower more focused work in process limit. So, it would be prudent to negotiate the commitment level on a couple of lower priority features from the release… and give the business a heads up this might happen.

This is one of the fastest ways to achieve a new inventory/WIP level in the system. If we are looking to show quick results and are able to negotiate a temporary change in service levels with the business, this can be a great approach.

This strategy is elaborated in depth in the Theory of Constraints body of knowledge.

No New Work

This is a more evolutionary version – don’t freeze current work, but deny new work until we reach the desired work in process levels. This means anyone finishing work on something will look at how he can help someone else, instead of starting something new. There will still be effects on the release commitment, but milder ones.

The price we pay here is that it will take more time to reach the new inventory/WIP level. It’s easier to negotiate with the business, but the results will show more slowly…

Visualize now, Limit Later

This is even a more evolutionary version. You start with Kanban principle #1 – Visualize work. You don’t put any WIP limits for now. You see how work looks like, you try to manage WIP, but don’t limit it. Perhaps when negotiating commitments to the next release V11 you take into account a period of cleaning the system/queues and the implications of lowering the WIP, and at that point you go into a Freeze/No New Work period, with a bit more confidence in how this will look like, based on a few weeks/months of visualizing your work.

This clearly is the risk-averse approach. Just be careful of running out of improvement energies and forgetting that just Visualizing Work is not enough…

Differentiated Service

A tweak on all of the approaches above can be to treat different work types differently. This is what we call Classes of Service in Kanban.

For example, Normal work above the WIP limit will be frozen. Fixed date work will hopefully be inside the WIP limit and be allowed to finish. New Fixed date work can be allowed to start, with the condition that a Normal work will be frozen in exchange for introducing it. If all work currently in the system is Fixed Date, we can decide whether to allow the new Fixed date to start (should be a comfort zone for most organizations 😉 or to have a serious discussion with the business on the risks it introduces and how we want to address them.

We can also say we visualize all work, but limit specific types of work.


What do you think about those approaches?

Which of the above did you find useful in real life?

Do you have other strategies for starting up in the real world?

Subscribe for Email Updates:



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