Book
Team Topologies
Organizing Business and Technology Teams for Fast Flow
Matthew Skelton, Manuel Pais
Summary
Matthew Skelton and Manuel Pais treat team design as an architectural decision rather than a reporting-line one. The book starts from Conway's law, the observation that the systems an organization builds mirror its communication structures, and argues that an org chart shows neither how work flows nor how much a team can hold in its head. Cognitive load becomes the constraint that decides how much a team owns. From there comes the model the book is known for: four team types, stream-aligned, enabling, complicated-subsystem, and platform, and three interaction modes, collaboration, X-as-a-Service, and facilitating. Alongside them sits the team API, stating what a team offers others and expects in return. A closing chapter on organizational sensing treats structure as something to evolve deliberately rather than freeze.
Target Readers
- Technical leaders deciding where to draw boundaries between teams, who want a vocabulary for it beyond the org chart
- Engineering managers whose teams own more surface area than they can reasonably keep in their heads, looking for a way to argue cognitive load as a design constraint
- Platform and enabling groups that need to state what they provide to other teams, and on what terms
Tags
Colophon
- Publisher
- JMA Management Center
- ISBN
- 978-4820729631
- Published
- Dec 2021
- List price
- ¥2,970incl. taxMay differ from the actual selling price on Amazon
Get this book
* The link above is an advertisement via Amazon Associates.Related Books
Prerequisites
- Recommended
The DevOps Handbook
How to Create World-Class Agility, Reliability, and Security in Technology Organizations
Gene Kim, Jez Humble, Patrick Debois, John Willis
Reason: Even if you adopt DevOps as a technical practice, fast flow won't emerge while the org structure stays siloed. Skelton & Pais's 'Team Topologies' presents organizational design that turns Conway's Law to your advantage via four team types and interaction modes, aligning the two wheels of technology and organization.
- Recommended
Clean Architecture
A Craftsman's Guide to Software Structure and Design
Robert C. Martin
Reason: Once you can design technical boundaries, you widen your view to the fact that those boundaries and team structure shape each other—Conway's Law. Architecture is not only a code problem but an organizational one.
- Recommended
Monolith to Microservices
Evolutionary Patterns to Transform Your Monolith
Sam Newman
Reason: As you carve out services, the question becomes whether the unit of decomposition matches the cognitive load of a team. The inverse Conway maneuver reorganizes teams to fit the architecture you want.
- Recommended
Learning Domain-Driven Design
Aligning Software Architecture and Business Strategy
Vlad Khononov
Reason: Once you can draw bounded contexts, you map those boundaries onto team structure. Aligning contexts with teams lowers cognitive load and speeds the flow of value.
- Related
Accelerate
The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations
Nicole Forsgren, Jez Humble, Gene Kim
Reason: The evidence in 'Accelerate'—that loosely coupled architecture and autonomous teams drive high performance—naturally calls for a concrete theory of organizational design. 'Team Topologies' offers the organizational patterns to implement that evidence, serving as a data-driven guide for structuring teams.
Next Books
- Recommended
Platform Engineering
A Guide for Technical, Product, and People Leaders
Camille Fournier, Ian Nowland
Reason: How to actually launch and run the 'platform team' that 'Team Topologies' advocates is its own discipline. Fournier & Nowland's 'Platform Engineering' covers the design, organization, and product strategy of internal developer platforms, connecting team-structure theory to concrete platform building.
- Recommended
Domain-Driven Design: Tackling Complexity in the Heart of Software
Eric Evans
Reason: After designing team boundaries for fast flow, you back those boundaries with the language of the business domain. A bounded context defines the outline of both the team and the model at once.
- Recommended
Architecture Modernization
Socio-technical alignment of software, strategy, and structure
Nick Tune, Jean-Georges Perrin
Reason: After grasping team structure and Conway's Law, you apply that thinking to the concrete context of legacy modernization. This book combines team topologies with Wardley mapping and domain decomposition, laying out a path to drive modernization across technology, organization, and strategy.
- Related
Site Reliability Engineering
How Google Runs Production Systems
Betsy Beyer, Chris Jones, Jennifer Petoff, Niall Richard Murphy
Reason: After designing an organization for fast flow of value with 'Team Topologies', you arrive at the question of which team owns reliability and how. Google's 'Site Reliability Engineering' presents concrete practices—error budgets, sharing of operational responsibility—for embedding reliability as organizational culture.