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:

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