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

Patterns for getting to a lower WIP level in a system

Facebook
Twitter
LinkedIn
Pinterest
WhatsApp

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.

Feedback

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:

Categories:

Tags:

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