Team Topologies Methodologies - Renavigating & Rescaling the Industry Standard for Containerization
summary
Docker reorganizes engineering around the Team Topologies model starting April 2021, replacing product-siloed groups with small stream-aligned teams (roughly 8–9 people, long‑lived) plus enabling, complicated-subsystem and platform teams; Docker first builds autonomy to ship customer features (registry, accounts, Hub/Desktop integrations), monetizes those gains, then adds cross-cutting platform teams (front-end platform, infra) to remove cognitive load. The claim: reduce handoffs and blocking dependencies by creating self‑service APIs and treat platform work as platform-as-a-product so teams actually ship faster.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 1:12Why do we write the book
- 5:21Flow of change
- 6:25Stream aligned team
- 9:02Supporting teams
- 11:42Team interaction modes
- 13:26Flow of change diagram
- 14:32Dependencies
- 16:38Getting Started
- 20:22Dockers Journey
- 28:40Phase 2 Implementation
- 31:32Mission Statements
- 32:41QA
- 35:16Cognitive Load
- 38:13Conways Law
- 42:38Streamline Teams
- 45:56Hiring
- 46:38Who are you helping
- 49:50Team Cognitive Load
- 52:54Remote Team Interactions Workbook
- 55:05Resources
- 57:17Example Section
related talks
46mBuilding memorable software engineering teams
54mThe value of Org Topologies in the era of DIY-frameworks
30mTeam Topologies Applied to Platform Engineering
30mThe Art of Team Design
37mDevOps Topologies 10 years on: what have we learned about silos, collaboration...
44mInsights on How Team Topologies Drive Organizational Success
37mPlatform as a Product for modern IT needs
07mSmall Teams vs Big Teams