The Scrum of Scrums (SoS) meeting is a key mechanism for coordinating multiple Scrum Teams. Its primary objective is to focus on integration and coordination by discussing progress, impediments, and dependencies.

Option (A) is correct because a central role of the Scrum Master is to remove impediments. The SoS provides a forum to identify, escalate, and coordinate the resolution of impediments that affect multiple teams.

Option (C) is also correct as the SoS is the primary venue for managing inter-team dependencies. Discussing actions that might affect other teams is crucial for ensuring smooth integration and preventing one team from blocking another. The Scrum Body of Knowledge (SBOK™ Guide) explicitly lists this as a key question to be addressed.

B. Discuss what each individual development team member has worked on since the last time all Scrum Masters met.

This level of detail is too granular. The Scrum of Scrums focuses on team-level coordination, not the tasks of individual members, which are discussed in the team's Daily Standup.

D. Share a status update on all individual team member' tasks.

This is incorrect for the same reason as option B. The SoS is a coordination and problem-solving meeting, not a detailed status report on individual tasks.

1. A Guide to the Scrum Body of Knowledge (SBOK™ Guide)

3rd Edition.

Page 188

Section 7.4

Scrum of Scrums Meeting: This section states

"This meeting is the forum for the representatives of the various Scrum Teams to discuss their respective progress

impediments

and dependencies." This directly supports both options A (impediments) and C (dependencies).

Page 188

Section 7.4

Scrum of Scrums Meeting: The guide lists four key questions for the SoS meeting. The fourth question is

"What is our team planning to do that might affect other teams?" This provides direct and explicit support for option C. The discussion of impediments supports option A.