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?

  1. Collecting detailed status from each developer across all teams
  2. Coordinating dependencies and integration among teams working on the same product
  3. Approving scope changes at the portfolio level
  4. 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.

AI Systems with Claude, for Scrum Masters and Project Managers

Most AI pilots in project management do not fail on the model. They fail because somebody pointed the thing at a decision instead of at a task. This course is built around that distinction, and around the work that follows once you get it right.

Eight teaching sections, taught against one running project from the first lecture to the last. You watch a system get built, then you build the same one against your own sprint. Nothing here is a demo that works only on the example.

You finish with five working systems and you keep them. The sprint report machine turns your board export and standup notes into the report you currently write by hand. The retro intelligence system tells you what the team keeps saying, not just what it said this time. The stakeholder comms engine drafts the update in the register the audience expects. The backlog health monitor flags the quiet decay nobody has time to check for. The risk and dependency tracker follows the chains that actually bite.

Seventy-six working files ship with it, across four sections, so every system is built against real sprint data rather than material invented for a slide. Four sprints of retrospectives, board exports, standup notes, backlog and risk data.

Explore the Course


Lead with clarity, influence, and outcomes.

HK School of Management and Technology offers a practical Leadership for Project Managers course for real projects, tight deadlines, and cross-functional teams. Learn to set direction, align stakeholders, and drive commitment without relying on title. Practical skills, tools, and guidance you can apply right away. Covered by Udemy's 30-day refund policy.

Learn More