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:

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