Engineering Team Topologies

Team Topologies is an approach to designing a team-of-teams organization for fast flow of value. It gives you a small pattern language for discussing team purpose, team boundaries, and interactions between teams.

The approach is not a fixed organization chart. You use it to understand the organization you have, design a better fit for the work, and adapt that design as the work changes.

Why team design affects delivery

A software system and the organization that builds it form one sociotechnical system. People, communication paths, responsibilities, and software boundaries affect one another.

Conway's Law captures one part of this relationship: system designs tend to reflect the communication structures of the organizations that create them. A boundary on an organization chart does not stay administrative. It influences who talks, where decisions happen, and how software components connect.

Team Topologies uses that relationship as a design input. You shape team boundaries and communication paths to support the flow and architecture you need.

The second design input is cognitive load. A team can own only so much domain knowledge, technology, operational work, and coordination before delivery slows. The other team types should help a stream-aligned team keep a manageable scope.

Start with the flow of value

A stream is a continuous flow of work for a product, service, customer journey, or business capability. A stream-aligned team owns a meaningful segment of that flow.