Representatives

A top-tier coordination meeting where delegates from related programs and projects in a program or portfolio gather on a set cadence or when needed. Attendees are representatives from each Scrum of Scrums. This extra layer is called the Scrum of Scrum of Scrums (SoSoS).

Key Points

  • Purpose: align multiple programs and projects, manage cross-program dependencies, and remove blockers that span several Scrum of Scrums.
  • Participants: representatives from each Scrum of Scrums, and when needed, program or portfolio leadership.
  • Cadence: held regularly or on demand; timeboxed and focused on decisions and impediment removal.
  • Outputs: clear actions, owners, due dates, and shared visibility of risks and decisions.

Example

A large portfolio has three programs, each with its own Scrum of Scrums. Every Wednesday, delegates meet in a SoSoS to resolve an enterprise-wide dependency on a shared payments API. They agree on an integration sequence, assign owners for fixes, and adjust program roadmaps to keep the release on track.

PMP Example Question

In a portfolio with multiple programs, each running its own Scrum of Scrums, where should a blocker that affects teams across several programs be escalated?

  1. The team Daily Scrum
  2. The program-level Scrum of Scrums
  3. The Scrum of Scrum of Scrums (SoSoS)
  4. The monthly PMO status review

Correct Answer: C — the top-level coordination meeting across Scrum of Scrums

Explanation: SoSoS exists to handle issues and dependencies that span multiple Scrum of Scrums, enabling cross-program decisions and rapid impediment removal.

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


Take Control of Project Performance!

HK School of Management helps you go beyond status reports and gut feelings. In this advanced course, you will learn Earned Value Management (EVM) to measure progress, forecast outcomes, and take corrective action. Learn how WBS quality drives performance, how control accounts work, and how to use EAC, TCPI, and variance analysis. Practical skills, tools, and guidance you can apply right away. Covered by Udemy's 30-day refund policy.

Learn More