In 30 seconds
- Representatives from each team meet regularly.
- Focus on cross-team dependencies and blockers.
- Keep it short, like a Daily Scrum for teams.
Who attends
One representative from each team, often a developer who knows current work, sometimes the Scrum Master. The person can rotate. Jeff Sutherland and Ken Schwaber described the practice in the mid-1990s.
What to discuss
- What has my team done that affects others?
- What will we do that affects others?
- What's blocking us, or about to block another team?
- Integration issues
Keeping it useful
- Short: 15 minutes, a few times a week or daily
- Problem-solving happens afterwards with only the people needed
- Track open cross-team issues visibly
See coordination mechanisms and Scrum@Scale.
Myth vs reality
Myth · It's a status meeting for managers.
Reality · It's for teams to coordinate.
Myth · Scrum Masters must attend.
Reality · Whoever best knows the work should go.
Myth · It solves problems in the meeting.
Reality · It surfaces them; solving happens after.
FAQ
How often should it meet?
Daily for tightly coupled teams; a few times a week otherwise.
How many teams can join?
Typically up to about nine; beyond that, add another level.
Is it part of the Scrum Guide?
No; it's a common scaling practice.