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 Retrospective occurs at the end of each Iteration, and the ART may also hold an Inspect and Adapt event at the end of a Program Increment to address systemic issues.

  Why this is correct

  The team Retrospective closes each Iteration by inspecting how the team worked and identifying improvements. In SAFe, the ART additionally holds an Inspect and Adapt event after the System Demo at the end of a Program Increment to solve broader, systemic problems. These operate at different levels and do not replace each other, giving teams both local and train-wide improvement loops.

• ✓

  Iteration Planning, the Daily Scrum, the Iteration Review, and the Retrospective all occur within the Iteration, while PI Planning occurs on the ART cadence across a Program Increment.

  Why this is correct

  Scrum events operate at the team level inside each Iteration, whereas PI Planning is an ART-level event held at the start of a Program Increment. Understanding that both cadences coexist prevents teams from treating PI Planning as a replacement for Iteration Planning. The Iteration remains the container for the team's Scrum events, and the Program Increment provides the broader alignment context around several Iterations.

• ✗

  An Iteration is the same length as a Program Increment, so the team holds one Iteration Review per PI and no Retrospective until the PI ends.

  Why it's wrong here

  A Program Increment typically spans several Iterations, so treating them as equal length contradicts SAFe's cadence structure. Holding only one Iteration Review per PI would eliminate the repeated inspect-and-adapt cycles that Scrum depends on and delay feedback for weeks. The Retrospective also occurs each Iteration, not once per PI, though the ART may hold additional Inspect and Adapt activities at PI boundaries.

• ✗

  The Daily Scrum should be replaced by the ART's Scrum of Scrums, because coordinating dependencies is more valuable than the team's daily inspection.

  Why it's wrong here

  The Daily Scrum is the Developers' event for inspecting progress toward the Sprint Goal and adapting their plan; the Scrum of Scrums is a separate coordination forum for the ART. Replacing one with the other removes the team's internal adaptation and leaves cross-team coordination without a team-level foundation. Both exist for different purposes and cadences, and neither substitutes for the other.

• ✗

  The Iteration Review and the System Demo are the same event, so a team that attends the System Demo does not need to hold its own Iteration Review.

  Why it's wrong here

  The Iteration Review is a team-level Scrum event where the team and stakeholders inspect the team's Increment, while the System Demo inspects the integrated solution across the ART. They serve different audiences and feedback loops. Skipping the Iteration Review would remove the team's own inspect-and-adapt opportunity and weaken Product Owner validation, even if the team participates in the System Demo.