liveBook · Manning

Team topologies

Team Topologies is an organizational design framework for structuring teams and their interactions to improve the flow of value in software delivery.

How 3 Manning books explain it

Architecture Modernization: Socio-technical alignment of software, strategy, and structure

A team topology is an arrangement of teams and their interactions within an organization.

How it is used
Uses team topologies to align organizational and software boundaries around independent value streams and expose obstacles to fast flow.
How deep it goes
Explains organizing principles, team-type and interaction patterns, and an interaction-mapping diagnosis; leaves topology evolution as an ongoing practice.
Examples
Maps a cosmetics brand’s integration platform team and its collaboration with at least four other teams to explain a bottleneck.
What you can do after
Apply it via Team Topologies to map team interactions, diagnose coordination bottlenecks, and refine candidate value streams.

Read how Architecture Modernization: Socio-technical alignment of software, strategy, and structure explains team topologies →

Effective Platform Engineering

A team topology is an organizational model that defines distinct team types and their interaction boundaries for effective software delivery.

How it is used
Aligns team boundaries and collaboration patterns with business value, platform consumption, specialized expertise, and capability development.
How deep it goes
Defines four team types and illustrates their responsibilities through platform-engineering and organizational-restructuring scenarios.
Examples
Uses e-commerce, mobile app, inventory management, platform services, CI/CD pipelines, and shared observability and identity services.
What you can do after
Apply team topologies to reduce silos, lower cognitive load, clarify ownership, and improve delivery speed, quality, and team morale.

Read how Effective Platform Engineering explains team topologies →

Microservices Patterns, Second Edition

Team Topologies is an organizational design framework for structuring teams and their interactions to optimize software delivery.

How it is used
Designs organizational structures and team interactions to support fast software delivery.
How deep it goes
Identifies four team types and interaction modes, but does not elaborate their operating practices.
Examples
Names stream-aligned, platform, enabling, and complicated-subsystem teams, with service consumption and collaborative interactions.
What you can do after
Evaluate whether organizational structure, DevOps, or architecture contributes to slow delivery before migrating to microservices.

Read how Microservices Patterns, Second Edition explains team topologies →

Also covered in

What to know first

Related concepts

Questions about team topologies

What is team topologies?

Team Topologies is an organizational design framework for structuring teams and their interactions to improve the flow of value in software delivery.

Which Manning books explain team topologies?

Architecture Modernization: Socio-technical alignment of software, strategy, and structure, Effective Platform Engineering and Microservices Patterns, Second Edition.

What should I know before learning team topologies?

Manning books that teach team topologies usually introduce cognitive load and self-service first.

What kinds of team topologies are there?

Kinds of team topologies include enabling team, engineering platform team, stream-aligned team and complicated subsystem team.

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.