Software Engineering Management at Scale with the Theory of Constraints
summary
Describes a concrete method that turns complex cross-team dependencies into a single linear priority queue using Theory of Constraints plus Drum‑Buffer‑Rope and Critical‑Chain ideas and Little’s Law forecasts. Uses metrics like buffer burn rate, virtual queue size and financial throughput rate to trigger swarms and escalation. Shows a case: 8,000 people, 120 engineering teams, ~400 concurrent projects and 70,000 change requests per month, delivering a reported 40% operational throughput uplift within months.
AI-written summary · about
chapters (33)
- 0:00Intro
- 2:10THE FOUR FLOWS OFTAMEFLOW
- 5:09SCOPE OF ACTION OF TAMEFLOW
- 5:57THE STORY OF HERBIE
- 8:08THE FIVE FOCUSING STEPS
- 9:20BUSINESS PERFORMANCE
- 11:13BUSINESS IS A BALANCE OF FORC
- 12:15SEPARATION OF CONCERNS
- 13:50MONEY AND MINIMAL TARGET SCC
- 14:34WHAT TIME IS IT?
- 16:32WHERE IS HERBIE? (1) THE WORK PROCESS CONSTRAINT
- 17:14FLOW TIME FORECASTS VIA LITTLE'S
- 18:42LIMIT WIP VIA DRUM-BUFFER-ROPE
- 20:27EXECUTION MANAGEMENT CCPM-ST WORK EXECUTION SIGNAL
- 21:22EXECUTION MONITORING: FEVER CH
- 22:30WORK FLOW - VALUE NETWORK
- 23:16FUTURE LOOKING: VIRTUAL QUEU
- 24:27REORDER THE MOVES BY FINANCIAL THROUGHPUT RATE
- 25:39WORK EXECUTION MONITORING FOR EACH TEAM
- 25:55THE BUBBLE FEVER CHART
- 26:38WHERE IS HERBIE? (3) THE WORK EXECUTION CONSTRAI
- 27:12DETECT IF/WHEN THE CONSTRAINT
- 29:54DEPENDENCY MANAGEMENT
- 31:24TYPES OF MOVES
- 32:20INTEGRATION WITH CPM / CCPM
- 33:25FLOW CHANNEL
- 34:34REMEMBER THE FLOW TIME AND THE FLOW TIME DISTRIBUTION?
- 34:44CUMULATIVE IN-STATE FLOW TIME DISTRIBUTIONS
- 35:05WORK ITEM AGEING
- 35:20DAILY STAND UP PROTOCOL
- 36:48BEHAVIOURAL RESPONSE
- 37:48PSYCHOLOGICAL FLOW TRIGGER
- 38:16DISCOVER MORE!
related talks
45mContinuous Delivery and the Theory of Constraints
21mHow TOC & CCPM Shifted Our Agile Mindset
41mSWARMing: Scaling Without A Religious Methodology
35mWhy Security Initiatives Are Doomed to Fail & What You Can Do About It
01h 01mSoftware Architecture, Team Topologies & Complexity Science
30mA framework for ambitious companies
32mPanel discussion: The journey to building effective engineering teams
44mTechnology is Necessary, But Not Sufficient