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:

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