What is the purpose of the scrum of scrums meeting during PI Planning?

A. To track planning progress across the ART

B. To create the program board

C. To discuss scope changes

D. To control WIP

The correct answer is

A. To track planning progress across the ART

Explanation

The purpose of the Scrum of Scrums meeting during PI Planning in the context of the Scaled Agile Framework (SAFe) is to track planning progress across the Agile Release Train (ART). This statement is true.

The Scrum of Scrums is a key mechanism in SAFe (and other Agile frameworks at scale) to ensure coordination and communication across multiple teams working towards a common goal, particularly during the Program Increment (PI) Planning event. Here’s a brief overview of how each option relates to the Scrum of Scrums meeting:

• To track planning progress across the ART: This is the primary purpose of the Scrum of Scrums during PI Planning. It facilitates cross-team synchronization and communication. Representatives from various teams meet to discuss progress, dependencies, impediments, and coordination needs to ensure that all teams are aligned and on track to meet the PI objectives.


• To create the program board: While the creation of the program board is a critical activity during PI Planning, it’s not the sole focus of the Scrum of Scrums meeting. The program board visualizes the plan for the PI, including features, dependencies, and milestones. Although discussions in the Scrum of Scrums may influence what appears on the program board, the board’s creation is a collaborative effort involving all stakeholders during the planning process.


• To discuss scope changes: Scope changes might be discussed during the Scrum of Scrums if they affect cross-team coordination and dependencies. However, the primary purpose of these meetings is not to discuss scope changes but to ensure alignment and track progress. Scope changes are typically addressed in more detail in other forums or discussions specific to the change’s impact.


• To control WIP (Work In Progress): Controlling WIP is an important aspect of Agile and Lean methodologies to ensure teams are not overloaded and can deliver value effectively. While the Scrum of Scrums may indirectly help control WIP by facilitating discussions on dependencies and impediments, its direct purpose is not to control WIP. WIP limits are usually managed at the team level and through practices like Kanban within the teams.

Therefore, the true purpose of the Scrum of Scrums meeting during PI Planning is to ensure that planning progress is being tracked across the entire Agile Release Train, facilitating effective coordination and communication among teams.

Other SAFe Scrum Master Question – How is team performance calculated in SAFe?