Team topologies
Team Topologies is an organizational design framework for structuring teams and their interactions to improve the flow of value in software delivery.
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.
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
- Collaborative Software Design: How to facilitate domain modeling decisions
- Simple Object-Oriented Design: Create clean, maintainable applications
What to know first
- cognitive loadCognitive load is the mental effort required to process information, retain it in working memory, or perform a task.
- self-serviceSelf-service is a mode in which users independently obtain resources or perform supported tasks without requiring an intermediary for each request.
Related concepts
- enabling teamincludes · An enabling team is a specialist team that helps other teams acquire capabilities and overcome technical or organizational obstacles without permanently owning their work.
- engineering platform teamincludes · An engineering platform team is an organizational team that builds, operates, and evolves internal platforms providing shared capabilities for software development and delivery.
- stream-aligned teamincludes · A stream-aligned team is a long-lived team organized around a continuous flow of customer or business value, with responsibility for delivering and maintaining its product or service.
- complicated subsystem teamincludes · A complicated subsystem team is a specialist team responsible for developing and maintaining a technically complex subsystem requiring deep expertise.
- Conway's lawused by · Conway’s law is the observation that a system’s structure tends to reflect the communication structure of the organization that designs it.
- durable teamuses · A durable team is a team that remains responsible for a product or value stream over an extended period rather than disbanding after a project ends.
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.


