HKSM
Scrum Of Scrums
A scaling practice where representatives from multiple Scrum teams building one product meet regularly to synchronize progress, manage inter-team dependencies, and plan how to integrate their work, especially where it overlaps.
Key Points
- Used when several Scrum teams collaborate on the same product.
- Attendees are team representatives (often Scrum Masters or ambassadors) empowered to act.
- Focuses on dependencies, impediments, risks, and integration across teams.
- Produces clear actions to resolve overlaps, handoffs, and cross-team blockers.
Example
Three Scrum teams building an e-commerce product hold a Scrum of Scrums twice a week. Team A (catalog) needs an API from Team B (search), and Team C (checkout) must integrate payment updates from Team A. In the Scrum of Scrums they align delivery dates, flag a security review dependency, and agree on a shared integration test plan before the next release.
PMP Example Question
Which activity best reflects the main purpose of a Scrum of Scrums in a multi-team product effort?
- Collecting detailed status from each developer across all teams
- Coordinating dependencies and integration among teams working on the same product
- Approving scope changes at the portfolio level
- Estimating stories and updating the backlog for a single team
Correct Answer: B — Coordinate cross-team dependencies and integration
Explanation: The Scrum of Scrums is a scaling coordination event to align multiple teams on dependencies, risks, and integration. It is not a developer status meeting, a portfolio governance forum, or a single-team planning activity.
