Scrum of Scrums Template for Agile Teams

Start with 3x per week (Monday, Wednesday, Friday). If dependencies are light, reduce to 2x per week. If you are in a critical release phase with tight integration timelines, go daily. The cadence should match the dependency complexity, not a fixed rule.

A program manager, release train engineer, or senior PM who has visibility across all teams. The facilitator should not be a team representative because they need to stay neutral and focus on coordination rather than their own team's priorities.

A standup is within a single team: each person shares their progress and blockers. A Scrum of Scrums is across teams: each team shares its collective progress and cross-team blockers. The SoS focuses exclusively on inter-team dependencies, not individual task updates.

Track them on the shared dependency board with all affected teams listed. Assign one person as the dependency owner who is responsible for coordinating across all teams. For complex multi-team features, consider creating a temporary integration team or assigning a technical program manager.

This usually signals one of three problems: the dependency was not identified early enough (improve grooming), the providing team does not have capacity (re-prioritize at the leadership level), or the requirement was unclear (improve the API contract or spec). Track dependency miss rates over time. If a specific team consistently misses deadlines, it needs a capacity or prioritization conversation, not more meetings.