SSM Supporting Team Events Practice Question
A Scrum Master notices that the team's Iteration Retrospective has become a status meeting where members report what they did rather than reflect on how they worked. Which action should the Scrum Master take to refocus the event on its intended purpose?
⚠ Common exam trap
The trap here is assuming that any deviation in a team event requires escalation or cancellation, rather than direct facilitation to restore the event's intended purpose.
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
✓
Introduce a structured format such as Start-Stop-Continue and explicitly ask the team to discuss process, interactions, and tools rather than task status.
The Retrospective exists for the team to inspect its process and identify improvements. When it devolves into status reporting, the Scrum Master should guide the team back to process-focused reflection. A structured format with explicit prompts about process, interactions, and tools achieves this while preserving team ownership and the event's purpose.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Ask the Product Owner to lead the Retrospective and prioritize the team's backlog based on reported progress.
Why it's wrong here
The Product Owner's focus is on value and backlog prioritization, not on facilitating team process reflection. Having the Product Owner lead the Retrospective would reinforce the status-reporting pattern and blur accountabilities. The Scrum Master is accountable for facilitating the Retrospective, so delegating it this way fails to solve the underlying issue.
- ✗
Cancel the Retrospective for the next Iteration and instead use the time for backlog refinement.
Why it's wrong here
Canceling the Retrospective removes the team's primary inspect-and-adapt mechanism for process improvement. Backlog refinement addresses product content, not team process. This action would undermine SAFe's principle of relentless improvement and leave underlying workflow issues unaddressed, making it an inappropriate response to a facilitation problem.
- ✓
Introduce a structured format such as Start-Stop-Continue and explicitly ask the team to discuss process, interactions, and tools rather than task status.
Why this is correct
Using a structured retrospective format and explicitly guiding the conversation toward process, interactions, and tools helps the team inspect how they work rather than what they did. This directly addresses the drift into status reporting and aligns with the Scrum Master's role of facilitating effective team events and fostering continuous improvement.
- ✗
Report the team's lack of retrospective focus to the Release Train Engineer and request that the team be coached on Agile principles.
Why it's wrong here
Escalating to the Release Train Engineer may be appropriate for impediments beyond the team's control, but this is a facilitation issue the Scrum Master should handle directly. Requesting external coaching without first attempting to refocus the event abdicates the Scrum Master's responsibility and may undermine the team's ownership of its own improvement.
About these practice questions
One of 385 original SSM practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.