SSM Supporting Team Events Practice Question
An Agile Team completes all their iteration backlog items two days before the end of the iteration. During the Iteration Planning meeting for the next cycle, the Product Owner asks why they didn't pull in extra work mid-iteration. How should the Scrum Master explain the team's action?
⚠ Common exam trap
Test-takers often penalize teams for finishing early, assuming high performance means constantly pulling in extra work and ignoring iteration goal stability.
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
✓
Pulling work mid-iteration risks the iteration goal, so the team focused on quality, testing, and technical debt.
Pulling new work mid-iteration destabilizes the iteration goal and disrupts focus. The Scrum Master should explain that finishing early allows the team to focus on technical debt, quality improvements, or helping other release train members rather than frantically pulling unrefined stories.
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 team took an unauthorized vacation for the remaining two days of the iteration.
Why it's wrong here
Taking unauthorised leave misrepresents the situation and implies misconduct where none exists. The team legitimately completed its Sprint Backlog commitment. This explanation would fit only if the team genuinely absented itself without agreement, which the stem does not describe.
- ✓
Pulling work mid-iteration risks the iteration goal, so the team focused on quality, testing, and technical debt.
Why this is correct
Completing backlog items early does not justify pulling unplanned work; the iteration goal and its acceptance criteria remain the commitment. The team instead used the remaining time for testing, refinement and technical debt, preserving quality and protecting the sprint's forecast from scope creep mid-iteration.
- ✗
The Scrum Master forbade the team from doing any work once the initial stories were completed.
Why it's wrong here
The Scrum Master has no authority to forbid work; that contradicts self-management and servant-leadership. The team's choice reflects their own judgement about Sprint Goal integrity. A Scrum Master would intervene this way only if the team were violating Scrum rules, not for finishing early.
- ✗
The team should have pulled in 20 more user stories immediately without refinement.
Why it's wrong here
Pulling in unrefined stories mid-iteration bypasses the team's Definition of Ready and Sprint Backlog commitment, risking scope creep and unvalidated work. Adding scope is legitimate only when the Product Owner negotiates it and the team confirms capacity, not as an automatic response to early completion.
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.