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:

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