- What is Conway's law, and why does it matter for team organisation?
- Conway's law, formulated by Melvin Conway in 1968, observes that a system ends up mirroring the communication structure of the organisation that builds it. For anyone leading engineering, this means the boundaries between teams become boundaries in the software, with their gaps and friction. Every decision about team structure is therefore also an architecture decision, whether you intend it or not.
- What is the inverse Conway manoeuvre, and when is it worth using?
- It means designing first the team boundaries you want to see reflected in the software, so that the architecture you want follows from them. Team Topologies popularised it. It is worth using when the diagnosis shows that teams and architecture are misaligned and working on the code alone is not enough, because the dependencies re-form every cycle. The decision should rest on data and be taken with the transition costs in view, since reorganising teams has a price in friction and learning.
- Do we have to adopt Team Topologies in full?
- No. Team Topologies offers a useful vocabulary, with team types and interaction modes, and we use it where it helps make explicit who does what for whom. What matters is that each team has a clear area of responsibility and can release independently, whatever the model is called.
- Feature teams or component teams?
- It depends on where the boundaries of your product lie. Feature teams own a feature end to end, without handing it to another group halfway, and they work well when the domain can be split into independent areas. Where part of the system needs very specialised skills, a team dedicated to that part can reduce the load on the others, provided its service to the other teams is explicit.
- Can you change the organisation without touching the architecture?
- You can, but it usually doesn't last. If the code still forces three teams to change the same modules, the dependencies come back whatever the org chart says. That is why we recommend supporting the new organisation in the code too, until each team fully owns the part of the system entrusted to it.