SSM Introducing Scrum in SAFe Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  The team's iterations should be replaced by ART-level cadence events so planning happens only at the Program Increment boundary.

  Why it's wrong here

  SAFe does not replace iterations with ART events; it aligns them. Iterations remain the team's basic planning and delivery cadence, and ART events such as PI Planning and the System Demo sit on top of them. Removing iterations would eliminate the team's short feedback loop and its ability to inspect and adapt every two weeks, undermining the empirical process Scrum depends on.

• ✗

  The team should hold its Retrospective only at the end of each Program Increment to align with the ART's Inspect and Adapt workshop.

  Why it's wrong here

  A Retrospective belongs at the end of every iteration, not only at the PI boundary. The ART's Inspect and Adapt workshop is an additional, larger-scale event that complements rather than replaces the team Retrospective. Deferring team retrospectives to PI boundaries would eliminate the frequent, short-cycle improvement loop that makes Scrum effective and would leave problems unaddressed for weeks.

• ✗

  The team's Daily Stand-up should be merged into the ART's Scrum of Scrums so status is reported once at the ART level.

  Why it's wrong here

  The Daily Stand-up is a team event for synchronizing and re-planning the day's work; the Scrum of Scrums is a separate ART-level event where representatives coordinate dependencies across teams. Merging them removes the team's own daily inspection and would turn synchronization into status reporting. The Scrum Master should keep these events distinct while showing how the team's daily coordination informs the Scrum of Scrums.

• ✓

  Team iterations and ART events run on the same cadence so that team-level inspect-and-adapt feeds the ART's PI cadence.

  Why this is correct

  In SAFe, team Iterations and the ART's events share a common cadence, with iterations nested inside the Program Increment. This alignment lets team-level learning flow into ART-level synchronization through events such as the System Demo and Inspect and Adapt. The Scrum Master clarifies this nesting so the team understands its Scrum events are not separate from, but integral to, the train's rhythm.