In 30 seconds
- Coordination is needed wherever teams depend on each other.
- Options range from shared planning to communities of practice.
- The best coordination is fewer dependencies.
Common mechanisms
| Mechanism | Use |
|---|---|
| Scrum of Scrums | Daily or weekly cross-team sync |
| Joint planning | Align at the start of each cycle, like PI Planning |
| Shared backlog | One ordered list for several teams |
| Communities of practice | Share skills and standards |
| Integration events | Combine work regularly |
Choosing mechanisms
Match coordination to dependency. Teams that rarely interact need little; teams sharing code daily need a lot. Start light and add only when problems appear.
Reduce the need first
Organize cross-functional feature teams around value, and use Team Topologies to define clear interactions. Less dependency means less coordination. See dependency management.
Myth vs reality
Myth · More meetings mean better coordination.
Reality · Better structure usually beats more meetings.
Myth · Coordination is a manager's job.
Reality · Teams coordinate directly where possible.
Myth · One mechanism fits all.
Reality · Mix and adjust to the situation.
FAQ
What's the lightest option?
Teams talking directly when they need to.
When do we need a coordination role?
When many teams share frequent dependencies.
How do we know coordination is working?
Fewer surprises at integration and fewer blocked items.