SSM Supporting Team Events Practice Question
A Scrum Master is preparing to facilitate the team's Iteration Retrospective after an iteration in which the team missed its Iteration Goals due to several unplanned production support requests. Which TWO actions best reflect the Scrum Master's responsibilities in supporting this event? (Choose two.)
⚠ Common exam trap
The trap here is thinking the Scrum Master should direct the Retrospective's outcomes or use it to address individual performance, when the role is to facilitate a safe, team-owned process that ends in owned improvement actions.
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
✓
Create a safe, non-judgmental environment where the team can openly discuss what happened and identify a small number of improvements to try in the next iteration.
The Scrum Master supports the Iteration Retrospective by creating a safe, blameless environment and by ensuring the event is timeboxed and produces a prioritized set of owned improvement actions. These two actions keep the team in control of its own improvement process while making the event productive. Dictating changes, evaluating individuals, or handing facilitation to an outside role all undermine the team's ownership and the Retrospective'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.
- ✓
Create a safe, non-judgmental environment where the team can openly discuss what happened and identify a small number of improvements to try in the next iteration.
Why this is correct
This is correct because the Scrum Master facilitates the Retrospective to be a safe, blameless space for inspection and adaptation. By fostering openness and guiding the team toward a few concrete improvements, the Scrum Master helps the team learn from the missed goals and the unplanned support work. The team owns the content and the actions, while the Scrum Master owns the process and the environment.
- ✗
Use the Retrospective to review each team member's individual performance against the missed Iteration Goals and document any shortfalls.
Why it's wrong here
This is inappropriate because the Retrospective is about inspecting the process and system, not evaluating individuals. Turning it into a performance review destroys psychological safety and discourages honest discussion. The Scrum Master should keep the focus on how the team works together and what systemic factors, such as unplanned support demand, affected the iteration, not on blaming people.
- ✗
Invite the Release Train Engineer to lead the Retrospective so that program-level concerns about missed goals are addressed directly with the team.
Why it's wrong here
Having the Release Train Engineer lead the team's Retrospective shifts ownership away from the team and can inhibit open discussion. While program-level issues may need attention, the team Retrospective should remain a team-owned event facilitated by the Scrum Master. If systemic concerns emerge, the team can raise them in appropriate program forums rather than ceding the Retrospective to an outside role.
- ✓
Ensure the Retrospective stays within its timebox and that the team leaves with a prioritized set of improvement actions, each with a clear owner and a plan to review progress.
Why this is correct
This is correct because effective Retrospectives are timeboxed and end with actionable outcomes. The Scrum Master helps the team converge on a prioritized set of improvements, assigns ownership, and establishes how progress will be checked. This prevents the event from becoming a vague discussion and increases the likelihood that the team will actually change its approach in the next iteration.
- ✗
Assign the team specific process changes that must be adopted in the next iteration to prevent any further unplanned support work.
Why it's wrong here
This fails because the Scrum Master does not dictate process changes to a self-managing team. Improvements should come from the team's own inspection and decisions during the Retrospective. Imposing changes undermines ownership and may not address the real causes of the unplanned support requests. The Scrum Master facilitates the team's discovery of improvements rather than prescribing them.
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.