Team Topologies

If the architecture of the system and the architecture of the organization are at odds, the architecture of the organization wins.

If the architecture of the system and the architecture of the organization are at odds, the architecture of the organization wins. Communication structures matter. Conway's law reveals that an organization's communication structure directly influences the design of the systems it creates. This principle has profound implications for software architecture and team organization. By aligning team structures with desired system architectures, organizations can leverage Conway's law to their advantage. Reverse Conway maneuver. Instead of letting team structures dictate system design, organizations can intentionally shape their teams to produce the desired architecture. This approach, known as the "reverse Conway maneuver," involves: Identifying the target system architecture Designing team structures that mirror this architecture Allowing the natural forces of Conway's law to guide development Strategic team design. By consciously designing team structures, organizations can: Encourage modular, loosely-coupled systems Promote clear interfaces between components Enhance system maintainability and scalability

Reducing cognitive load for teams and facilitating team interactions helps to optimize flow. Cognitive load matters. The team-first approach recognizes that there's a limit to the complexity a team can effectively manage. By prioritizing team cognitive capacity, organizations can: Enhance productivity and innovation Reduce stress and burnout Improve code quality and system reliability Strategies for managing cognitive load: Limit team responsibilities to match their cognitive capacity Break down large systems into team-sized components Provide clear, well-defined interfaces between teams Invest in tools and platforms that simplify complex tasks Optimizing for flow. By reducing unnecessary cognitive burdens, teams can achieve a state of flow, characterized by: High productivity and creativity Increased job satisfaction Faster problem-solving and innovation

The four fundamental Team Topologies are: stream-aligned, enabling, complicated subsystem, and platform. Stream-aligned teams form the backbone of the organization, delivering value directly to users or customers. They are: Cross-functional Aligned to a specific product, service, or user journey Empowered to deliver end-to-end value Enabling teams support and accelerate stream-aligned teams by: Providing specialized expertise Conducting research and prototyping Facilitating knowledge transfer Complicated-subsystem teams manage complex components that require deep expertise, allowing stream-aligned teams to focus on delivering value. Platform teams provide internal services and tools that empower stream-aligned teams to work more efficiently and autonomously. By adopting these four team types, organizations can: Clarify team responsibilities and interactions Reduce dependencies and bottlenecks Enhance overall delivery speed and quality

Limiting team interaction to three modes—collaboration, X-as-a-Service, and facilitating—simplifies and clarifies essential interactions between teams building software systems. Collaboration mode involves close teamwork for discovery and innovation. It's best used: During early phases of new system development For solving complex, cross-cutting problems When rapid learning and adaptation are crucial…