HKSM

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.