Team Topologies Panel
summary
Panelists report that adoption is uneven: stream-aligned and platform as a product practices appear widely, while enabling teams and complicated subsystem teams cause confusion and funding problems. Organizations under-adopt the concrete fast‑flow practices and fracture‑plane analysis despite their value; a concrete example is an SRE/product conflict resolved by changing interaction mode. Practical fixes include mapping blockers to flow, short local rules to allow ad‑hoc help (two × 30 minutes), clarifying terms per org, and treating teams as an ecosystem rather than isolated islands.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 4:20Questions
- 7:50Fracture planes
- 9:05Fast flow principles
- 13:20Problems and difficulties
- 14:08Enabling teams
- 17:05Complicated subsystems
- 25:30Enabling culture
- 29:52Blockers to flow
- 35:02Early adopters
- 37:07Streamlined teams
- 41:22Interactions
- 49:30Question
related talks
30mTeam Topologies Applied to Platform Engineering
45mLessons learned from introducing Team Topologies
30mProduct Teams Need A Family Too
41mWhy one model can’t fit all creating fulfilling engineering organizations
37mPlatform as a Product for modern IT needs
35mHow a Lean and Structured Team Topology amplifies an Organisation's Productivity
01h 00mPanel
45mSystems Thinking by combining Team Topologies with Context Maps