Ring-fence the Chaos: When Technical Teams Meet Organisational Systems
summary
Shows how a real org cuts delivery delays by isolating ad‑hoc work into a dedicated team chaos (support/maintenance) and using a floating skill pool so projects keep moving when people are on leave, with the build team on Scrum, design on waterfall and support on Kanban. Demonstrates concrete failures—database provisioning stretched to three weeks for a one‑minute task, a 130‑project VS solution taking 10+ minutes to build—and explains the exact team configs and process changes that reduce those bottlenecks.
AI-written summary · about
chapters (23)
- 0:00Introduction
- 0:38What motivated this talk
- 1:54A story
- 2:43The process
- 5:52How to know if youre a bottleneck
- 7:21Measuring efficiency
- 10:08Policies and processes
- 11:09When can we start
- 11:39One person unavailable
- 12:35Resourcing
- 13:44Team Configuration
- 20:31Friction
- 22:01Systems
- 23:56Breaking away from old systems
- 25:12Ruffled feathers
- 26:25Team maturity
- 27:43Waterfall
- 31:36Maturity
- 33:45Scrum
- 34:45Mature Teams
- 36:16Interdependency
- 36:51Ringfence the Chaos
- 40:11Summary
related talks
40mPersonnel Chaos Engineering and Building a Resilient Organizational Structure
05mKill the Project. Build a Team.
46mLeading Distributed Teams
43mBetter Software Development Systems through Stress
56mDefending against CDD: Chaos-Driven Delivery
29mThe four components of high performing teams
36mLeadership During Chaos
43mSoftware Engineering Management at Scale with the Theory of Constraints