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:

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