SSM Supporting Team Events Practice Question
During an Iteration Retrospective, a Scrum Master facilitates a team that has identified several process problems but is now stuck in vague complaints. The Scrum Master wants to help the team produce a small number of actionable improvement items that can be completed within the next iteration. (Choose two.)
⚠ Common exam trap
The trap here is thinking that more analysis or a longer meeting will produce better improvements, when the real need is structure and a small number of owned 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
✓
Ask the team to limit improvements to one or two items and assign a single owner and due date for each.
When a team is stuck in vague complaints, the Scrum Master should introduce structure and limit the number of improvements. Start-Stop-Continue converts observations into concrete behaviors, while limiting improvements to one or two with a single owner and due date creates accountability. Together these practices help the team produce actionable outcomes within the iteration and avoid the trap of overcommitting to too many changes.
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 team to limit improvements to one or two items and assign a single owner and due date for each.
Why this is correct
Limiting improvements to one or two items prevents the common failure of overcommitting and then abandoning all actions. Assigning a single owner and a due date creates accountability and makes follow-up possible. This practice aligns with SAFe's emphasis on small, incremental improvements and with the Scrum Master's role in helping the team take ownership of its process. It also ensures the retrospective produces outcomes rather than just discussion, which is essential when the team is stuck.
- ✗
Extend the retrospective by an hour to ensure every complaint is fully analyzed before selecting improvements.
Why it's wrong here
Extending the timebox to analyze every complaint can deepen frustration and delay action. The retrospective is time-boxed for a reason; teams often need to converge rather than exhaustively analyze. More discussion does not guarantee better outcomes and can reinforce the pattern of vague complaints. The Scrum Master should help the team focus on a few high-impact improvements, not spend additional time cataloging every issue. Longer meetings also risk reducing the team's available iteration time.
- ✗
Ask each team member to write a personal improvement goal and track it privately without team discussion.
Why it's wrong here
Private individual goals remove the collective ownership that makes retrospectives effective. SAFe emphasizes team-level inspect and adapt, and improvements that are not shared cannot be supported or measured by the team. While personal growth is valuable, the retrospective's purpose is to improve how the team works together. This option also makes follow-up impossible, since the team cannot inspect progress on goals it cannot see, and it may hide systemic issues that require group action.
- ✓
Guide the team to use a structured format such as Start-Stop-Continue to convert observations into specific behaviors.
Why this is correct
Structured formats like Start-Stop-Continue help teams move from general complaints to concrete behaviors that can be changed. This technique gives the team a shared language for categorizing observations and naturally yields actionable items. It also keeps the retrospective focused and time-boxed, which is important when the team is stuck. By turning vague statements into specific starts, stops, and continues, the team can select a few improvements that are realistic for the next iteration.
- ✗
Document all identified problems in the team's backlog so the Product Owner can prioritize them alongside features.
Why it's wrong here
Retrospective improvements are about the team's process, not product features, so placing them in the product backlog mixes concerns and dilutes ownership. The Product Owner prioritizes value delivery, not team process changes. While some technical debt items may become backlog items, the retrospective's process improvements should remain with the team. This option also risks burying actionable improvements behind feature work, which would prevent the team from making progress on its own effectiveness.
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.