Team topologies

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

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

A team topology is an arrangement of teams and their interactions. It matters because software boundaries alone cannot create fast flow: if teams must repeatedly change the same code or coordinate deployments, organizational friction remains. Aim to align team responsibilities and software boundaries around value streams that can move as independently as practical, while recognizing that some dependencies will remain. section 11.0 section 11.1.6

Team Topologies provides principles and patterns for shaping that arrangement. Its patterns describe four team types and three interaction modes, but labels are not a substitute for the principles behind them. A stream-aligned team, for example, owns a value stream from discovering user needs through operating its software. Shared platform capabilities can reduce the cognitive load that would otherwise distract such teams from their core work. section 11.2 section 11.2.1

An overloaded integration team

At a global cosmetics brand, an integration platform team built and maintained custom endpoints for several other teams. Mapping its interactions revealed collaboration with at least four teams. The coordination required exceeded its capacity, making it a bottleneck. The map made the problem discussable without treating the team’s effort as the cause. section 11.2.3

Figure 11.6 The integration platform team was overloaded with too much collaboration.

Use the interaction map to see how multiple collaboration relationships concentrated coordination on the integration platform team. section 11.2.3

To examine a candidate topology together:

• Map teams against their value streams and software boundaries. Look for shared code, synchronized deployments, and decisions outside a team that interrupt its flow. section 11.0 section 11.1.6
• Identify each team’s role and its interactions. If a team appears to occupy several roles, ask whether its responsibilities are too broad; do not force an existing team into a label. section 11.2.1
• Check whether responsibilities and coordination demands fit the team’s cognitive load. Revisit the map as needs change rather than treating a reorganization as a finished design. section 11.6 section 11.4

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

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 it assumes

Assumes a context of teams and software architecture while defining value-stream responsibilities and introducing team types and interaction modes.

What you can do after

Apply it via Team Topologies to map team interactions, diagnose coordination bottlenecks, and refine candidate value streams.

How it connects

Connects team topologies to Conway’s law, value streams, domain boundaries, cognitive load, and software architecture.

liveBookmanning.com

Read Architecture Modernization: Socio-technical alignment of software, strategy, and structure on liveBook Get the book at manning.com

Also explained in

• 

  liveBookmanning.com
  Effective Platform EngineeringA team topology is an organizational model that defines distinct team types and their interaction boundaries for effective software delivery.

Compare how 2 books explain team topologies →

Related concepts

• 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.
• 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.
• 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.
• independent service heuristicsused by · Independent service heuristics are a set of heuristics for assessing the independence of a value stream and identifying concerns that may limit its effectiveness.
• 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.

This explainer was generated by Manning's knowledge graph from the text of Architecture Modernization: Socio-technical alignment of software, strategy, and structure. The section links point to the parts of the book it draws on.