DevOps Topologies 10 years on: what have we learned about silos, collaboration...
summary
Team Topologies plus State of DevOps lessons push three concrete moves: reorganize around Accelerate metrics and flow, use heuristics and Team interaction modeling to find service boundaries, and measure cost of waiting — a worked example shows one hour blocked per engineer per day becomes millions per year. Case studies include 60% fewer dependencies at JP Morgan after reshaping teams and 40% cloud cost reduction in the UK Home Office; tools cited: Teamform and Teos.
AI-written summary · about
chapters (10)
- 0:00Introduction and retrospective
- 3:24Origins of DevOps Topologies
- 10:10Key lessons from State of DevOps reports
- 13:21Cost of tangled software dependencies
- 16:09Organizing for fast flow and efficiency
- 22:05Principles for evolving at speed
- 26:41Success stories with fast flow
- 31:00Active knowledge diffusion across teams
- 35:10What holds back low performers
- 36:32Summary and call to action
related talks
37mFrozen DevOps? Team Topologies Comes to the Rescue!
54mFrozen DevOps, The Not so technical Last Mile
44mInsights on How Team Topologies Drive Organizational Success
40mHow did our DevOps team become another silo?
47mWhy We Need DevOps Now: A Fourteen Year Study Of High Performing IT Organizations
28mDevOps, 12-Factor, and Platform Engineering
18mScaling DevOps in Complex Environments: Challenges, Failures, and Successes
26mTen (Hard-Won) Lessons of the DevOps Transition