SSM Introducing Scrum in SAFe Practice Question
An enterprise is introducing Scrum within a SAFe transformation. Leadership asks which two outcomes a Scrum Master should expect from a healthy, well-run Iteration Retrospective. Which TWO options represent valid outcomes? (Choose two.)
⚠ Common exam trap
Test-takers frequently assume retrospectives are meant primarily for assigning blame for missed sprint goals or reporting status to management.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
One or two concrete, actionable improvement stories added to the team backlog for the upcoming iteration.
A healthy Iteration Retrospective results in tangible, prioritized improvement backlog items that the team commits to implementing in the next iteration. It also provides a safe, transparent environment where team members openly inspect their interpersonal dynamics and process friction to drive continuous learning.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
A comprehensive report of individual employee performance metrics submitted to human resources for annual reviews.
Why it's wrong here
Retrospectives examine process and system conditions, not individual performance data; compiling per-employee metrics for HR turns the event into appraisal evidence and suppresses candour. Individual performance reporting belongs to people-management processes. Valid outcomes are team-identified improvements the Scrum Team owns and can implement.
- ✓
One or two concrete, actionable improvement stories added to the team backlog for the upcoming iteration.
Why this is correct
Retrospectives must produce tangible adaptation, not just discussion. Converting agreed improvements into one or two actionable stories placed on the team backlog ensures the next iteration actually carries the change forward, satisfying SAFe's expectation of continuous, tracked team improvement.
- ✓
A safe space for the team to inspect their processes, collaboration, and interpersonal dynamics openly.
Why this is correct
Creating psychological safety where team members can transparently discuss what went well and what failed is the hallmark of an effective retrospective. Open dialogue allows teams to address root causes of friction before they compound into systemic failures.
- ✗
A finalized list of updated enterprise strategic themes approved by executive portfolio management.
Why it's wrong here
Strategic themes are set by portfolio management during Lean Portfolio Management events, outside the team's Retrospective. Finalising them there inverts SAFe's flow of strategy to execution. A Retrospective instead produces team-level process improvements the team can act on within the next Iteration.
- ✗
A mandate from management changing the team's definition of done without team input or consensus.
Why it's wrong here
A management-imposed definition of done bypasses the team's own agreement, which the Retrospective exists to inspect and adapt. Such mandates arrive through portfolio governance, not team inspection. A valid outcome is a team-owned improvement to its working agreement, decided by those doing the work.
About these practice questions
Courseiva writes every SSM question from scratch — 385 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Scaled Agile exam blueprint
This SSM practice question is part of Courseiva's free Scaled Agile certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SSM exam.