Understanding the relationship between Kanban and the Theory of Constraints Critical Chain Project Management Approach

Facebook
Twitter
LinkedIn
Pinterest
WhatsApp

Background

I recently had a short twitter chat with Catherine Swetel and Steven Holt about the relation between TOC Critical Chain and Kanban. This post will try to sum up my thoughts in a way that is a little bit more persistent, as well as add a bit more color and depth that is not possible in 140 characters. To start with, lets just make clear – I’m no expert at TOC or Critical Chain. I’ve done my share of reading over the years and have seen organizations using CC and helped them explore the Agile/Kanban world. I’ve read Critical Chain for the first time back in 1996 or so and also familiarized myself with the MPCC S&T tree in the last couple of years. With that disclaimer, here are my thoughts, for what they’re worth:

Multi-Project / Program Level

If you start at the project/portfolio level, I see the Multi-Project Critical-Chain and especially its Strategy and Tactics tree as very similar to the Kanban System for driving improvement. Both approaches start with Limiting Work in Progress at the Projects level as key to reducing unhealthy multi-tasking and improving predictability and effectiveness. With time, excess capacity can be used to shape demand and create new exciting business models. I think the CC world is more advanced in its view on this aspect, but the Kanban world is certainly going there. We would be wise to learn from Viable Vision and other great thinking in the TOC world.

The Feature Design Factory

Once inside a project, kanban advocates a feature driven approach to development. The understanding that product development is a knowledge discovery process where units of inventory start as options and end up being working tested validated features is at the core of the Agile approach. The assumption is that we are operating in an uncertain environment. Both the requirements/problem as well as the technology/solution has considerable elements of uncertainty. We welcome this uncertainty as it comes together with the opportunity for great returns. We also recognize that Integration activities hide a lot of the risk in our projects, and so we drive for early and continuous integration to minimize that risk.

The way to operate effectively in this environment is to have a continuous process of focusing on a few features, seeking feedback along the development process all the way to customer/field feedback, orienting ourselves based on it iterating thru the same or earlier stage of the process depending on the feedback, and at the end having a marketable/viable feature that doesn’t hid any more work behind it. Only then do we pull another option/feature and drive it thru the process.
Kanban realizes that we have a certain capacity of features we can effectively process at any point in time. Overburdening this capacity will mean the knowledge discovery for each feature will take longer and the feedback will be handled later at a higher cost. I’m guessing this will resonate with any TOC practitioner. And indeed, the realization that features can be handled as inventory opens the door to applying a lot of the pure TOC thinking.

This approach can be used for handling an ongoing product development context where there is always plenty of options that can provide business value, and we are a factory/studio choosing the best option to develop and deliver.

Managing Projects with Kanban

When the context is a major project comprised of many different capabilities/features, this approach works as well. There might be a stronger need to manage the overall project health, but the basic principles still apply. There was an interesting discussion about this lately in the kanbandev user group. I also covered this in my recent talk about Commitments in a Kanban world. In this area, I believe CC provides us with good practices and tools – Release Burnup/CFD charts can evolve to Fever charts for each project, and an overall Fever chart managing the overall projects portfolio.

Typically, breaking projects to features will result in quite a simple dependency graph/pert chart. This is because the network is comprised of self-sufficient features. Sometimes though, Features do have dependencies on each other, or dependencies on external groups, as well as need to be delivered independently before the major delivery. When this list of dependencies grows larger and larger, maintaining a Critical-Chain view of the project/program together with relevant feeding buffers might make more and more sense. This view should only care about Features with dependencies, so it is typically quite simple, ideally managed as a Big Visible Chart on a project wall, a Look-Ahead plan, etc.

The Feature Design Factory

Once inside a project, kanban advocates a feature-driven approach to development. The understanding that product development is a knowledge discovery process where units of inventory start as options and end up being working tested validated features is at the core of the Agile approach. The assumption is that we are operating in an uncertain environment. Both the requirements/problem, as well as the technology/solution, have considerable elements of uncertainty. We welcome this uncertainty as it comes together with the opportunity for great returns. We also recognize that Integration activities hide a lot of the risk in our projects, and so we drive for early and continuous integration to minimize that risk.

The way to operate effectively in this environment is to have a continuous process of focusing on a few features, seeking feedback along the development process all the way to customer/field feedback, orienting ourselves based on it iterating thru the same or earlier stage of the process depending on the feedback, and at the end having a marketable/viable feature that doesn’t hide any more work behind it. Only then do we pull another option/feature and drive it thru the process.
Kanban realizes that we have a certain capacity of features we can effectively process at any point in time. Overburdening this capacity will mean the knowledge discovery for each feature will take longer and the feedback will be handled later at a higher cost. I’m guessing this will resonate with any TOC practitioner. And indeed, the realization that features can be handled as inventory opens the door to applying a lot of pure TOC thinking.

This approach can be used for handling an ongoing product development context where there is always plenty of options that can provide business value, and we are a factory/studio choosing the best option to develop and deliver.

Managing Projects with Kanban

When the context is a major project comprised of many different capabilities/features, this approach works as well. There might be a stronger need to manage the overall project health, but the basic principles still apply. There was an interesting discussion about this lately in the KanbanDev user group. I also covered this in my recent talk about Commitments in a Kanban world. In this area, I believe CC provides us with good practices and tools – Release Burnup/CFD charts can evolve into Fever charts for each project, and an overall Fever chart manages the overall project portfolio.

Typically, breaking projects into features will result in quite a simple dependency graph/pert chart. This is because the network is comprised of self-sufficient features. Sometimes though, Features do have dependencies on each other, or dependencies on external groups, as well as needing to be delivered independently before the major delivery. When this list of dependencies grows larger and larger, maintaining a Critical-Chain view of the project/program together with relevant feeding buffers might make more and more sense. This view should only care about Features with dependencies, so it is typically quite simple, ideally managed as a Big Visible Chart on a project wall, a Look-Ahead plan, etc.

Another approach I touch on elsewhere (including the commitment talk mentioned above) is to classify the work based on need for shared resource and affecting routing decisions based on that. So if a specialist or any other type of shared resource is currently congested, consider pulling work that doesn’t require much of his involvement. Or even better, pull work that will reduce your dependency on him in the future.

Summary

Well, These are just some thoughts, an invitation for future discussion. I believe there is potential for a lot of synergy between Kanban and CC, especially in the world of complex programs/portfolios. I especially urge the TOC/CC practitioners out there to explore the “Feedback Oriented” view of Agile. What we all need to remember is that the main thing about the Kanban method is that it is aimed at catalyzing evolutionary improvement. It is similar to the aim of the TOC S&T trees trying to drive towards a Viable Vision. Don’t get confused by the mechanics. The key is to use the conversations that happen when it is painful to follow an explicit process policy, like maintaining a WIP limit, to learn something and improve.

And if you are currently using Critical Chain and would like to explore what Kanban or Agile might mean or how they can help you, I’d love to help.

Subscribe for Email Updates:

Categories:

Tags:

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