Software Architecture, Team Topologies & Complexity Science
summary
Argues organizations must optimize the flow of value and shows concrete practices that do this: Amazon-style forcing functions (teams must use externalized interfaces, two‑pizza limits) produce a measured superlinear revenue scaling of 1.15 exponent as headcount doubles, versus the usual 85% scaling decline; long value streams in large firms take 6–9 months and cause queues. Recommends team patterns—stream-aligned teams, enabling and platform teams—plus value‑stream mapping, architectural fitness tests and policy as code in pipelines to unblock flow.
AI-written summary · about
chapters (13)
- 0:00Intro
- 6:48Team Topologies & complexity
- 11:28What is value?
- 13:29Team Topologies
- 14:45Software architecture & complexity
- 20:10Complex adaptive systems
- 26:38Complex adaptive systems are everywhere
- 27:21Corporate metabolism
- 34:53Sidebar: Identifying the signs of ageing
- 36:30Organisational mortality
- 37:52Scaling complex adaptive systems
- 47:32Resources
- 48:01Q&A
related talks
49mSoftware Architecture, Team Topologies & Complexity Science
39mTeam Topologies, Software Architecture & Complexity
53mKeynote - Software Architecture, Team Topologies and Complexity Science
37mScale, Flow and Microservices
48mScale, Microservices and Flow
42mScale, Flow and Microservices
56mOptimizing for a fast flow of value with adaptive, socio-technical systems
30mMoving Fast At Scale