Loading content
The Team Topologies concept provides a framework for designing and optimizing team structures within organizations. It helps to understand and improve interactions between teams to enhance efficiency and effectiveness in software development.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Theoretical construct: explains a term, principle, or mental model.
What you need to understand to reason about a domain.
Team Topologies is an organizational model that shapes teams around their responsibility and interaction for fast, sustainable flow of value.
Matthew Skelton and Manuel Pais developed Team Topologies through their work on team structures and software delivery; their 2019 book combined four team types and three interaction modes into a flow-oriented organizational approach.
Picture a river system: stream-aligned teams deliver value, platform teams clear the route, enabling teams remove obstacles, and complicated-subsystem teams contain specialist knowledge. Interaction modes define whether teams collaborate, provide a service, or help temporarily.
Teams are shaped around flow of value and cognitive load.
Four team types divide responsibilities and specialist knowledge.
Three explicit interaction modes limit coordination costs.
Team Topologies helps organize ownership, platforms, and dependencies in digital products. It fits growing teams; its types do not replace a diagnosis of the organization at hand.
Where this building block is located in the topic model.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.