Laws of Software Engineering · Pattern
Pattern
Team Topologies
Four kinds of team (working on a stream of value, building a platform, helping others, or owning something complicated). Three ways teams can interact (working together, providing a service, or helping someone learn).
How to use it. Default every team to the value-stream type. Justify any other type. Be explicit about how teams interact and for how long.
How it gets misused. Renaming existing teams without changing how they work. The topology lives in the interactions, and the labels alone change nothing.
Related
-
Pattern
Conway's Law
The shape of your software ends up matching the shape of how your teams talk to each other.
-
Principle
Cognitive Load
The mental effort needed to understand or change a system. There is a fixed budget per person and per team.
- Pattern Dynamic Reteaming Teams change shape over time. People join, leave, split, and merge. Treat reteaming as a normal practice.
Clusters
- The Team Design cluster - How to organise people for software work.