SSM Supporting Team Events Practice Question
Exhibit
Team Velocity Trend: Iteration 1: 30, Iteration 2: 32, Iteration 3: 25, Iteration 4: 28.
Refer to the exhibit. Given the velocity fluctuations, what is the best topic for the team's next Retrospective?
⚠ Common exam trap
Candidates often suggest ignoring the fluctuation as a 'normal' variance, failing to realize that large spikes or drops are signals of process instability.
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
✓
Discuss why the velocity dropped in Iteration 3 and what caused the variation.
Velocity fluctuations are a signal for the team to investigate what factors hindered their consistency. By analyzing the dip in Iteration 3 and the subsequent recovery, the team can identify process bottlenecks or external dependencies that affected their performance. This investigation is essential for the team to become more predictable and to ensure they are accurately forecasting their capacity for future planning cycles.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Discuss why the velocity dropped in Iteration 3 and what caused the variation.
Why this is correct
Analyzing the variance is the correct approach to improving predictability. When a team understands the cause of velocity dips, they can take proactive steps to mitigate those risks in the future. This builds trust with stakeholders and allows for more accurate planning in future Program Increments and iterations.
- ✗
Set a higher velocity target for the next iteration to encourage the team to work faster.
Why it's wrong here
Setting arbitrary targets for velocity is a common anti-pattern that encourages gaming the system. Velocity is a measurement of capacity, not a performance metric to be beaten. Pressure to increase velocity artificially leads to poor quality and technical debt, which ultimately slows the team down in the long run.
- ✗
Inform the team that their velocity is inconsistent and needs to stabilize immediately.
Why it's wrong here
Simply telling the team they are inconsistent does not help them solve the underlying problems. The Scrum Master should facilitate a constructive dialogue that empowers the team to investigate their own work processes, rather than just delivering criticism that may lead to frustration and disengagement within the team.
- ✗
Compare the team's velocity against other teams to ensure they are performing well.
Why it's wrong here
Comparing velocity between teams is fundamentally flawed because each team has a unique context, skill set, and story point definition. This practice creates unnecessary competition and destroys collaboration. The Scrum Master must protect the team from such comparisons and keep the focus on their own internal improvement process.
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.