Defending against CDD: Chaos-Driven Delivery
summary
Argument applies OS process management to team flow and gives concrete tools: surveys of first-come-first-served, shortest-job-first, priority, round-robin, a working multi-level feedback queue with per-queue scheduling and promotions/demotions, a CNN/Turner implementation example, capacity experiments that dedicate a focused pool of people, tactics like cross-training, minimum allocations for maintenance and work-in-process limits, and a striking claim that each dependency roughly doubles the chance of missing a deadline (four deps → 1 in 16).
AI-written summary · about
chapters (6)
- 0:00Start
- 5:23The (vicious) cycle of pain
- 14:12Round Robin
- 18:23Consider the different time scales
- 39:53Process synchronization
- 47:04And, make focus a priority
related talks
05mCombat Chaos-Driven Delivery By Thinking Like An OS
42mRing-fence the Chaos: When Technical Teams Meet Organisational Systems
43mSoftware Engineering Management at Scale with the Theory of Constraints
46mLeading Distributed Teams
50mHow Flow Works
01h 04mPredictably Unpredictable
01h 00mHow Work Works
38mScientific and Safe Chaos Engineering