SSM Supporting Team Events Practice Question
During an Iteration Review, a stakeholder asks the team to demonstrate a feature that was completed but not yet integrated with another team's component. The team cannot show it working end to end. What is the most appropriate Scrum Master action to support the event?
⚠ Common exam trap
The trap here is believing the team should present a polished demonstration even when integration is incomplete, rather than being transparent about the dependency and using the event to surface it.
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
✓
Facilitate the team in transparently explaining the integration dependency and capture it as an impediment to address with the other team.
The Scrum Master supports the Iteration Review by protecting transparency and helping the team honestly communicate its actual state. When a feature is not integrated, the team should acknowledge the dependency, capture it as an impediment, and use the event's feedback to plan the next steps rather than masking the gap.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Instruct the team to demonstrate the feature using mock data so the stakeholder sees the intended behavior.
Why it's wrong here
Demonstrating with mock data misrepresents the actual state of the Increment and undermines the Iteration Review's purpose of inspecting real progress. It hides the integration gap, prevents the stakeholder from giving informed feedback, and delays addressing the dependency. Transparency, not a polished demo, is what the Scrum Master should protect.
- ✗
Ask the stakeholder to postpone their question until the next System Demo so the team can prepare a proper demonstration.
Why it's wrong here
Deferring the question avoids the transparency the Iteration Review exists to provide. The event is the team's opportunity to show what is done and to surface issues early. Postponing to the System Demo may be appropriate for a broader audience, but it does not excuse the team from honestly addressing the integration gap now.
- ✓
Facilitate the team in transparently explaining the integration dependency and capture it as an impediment to address with the other team.
Why this is correct
The Scrum Master supports the Iteration Review by helping the team be transparent about what is and is not integrated. Acknowledging the dependency and capturing it as an impediment keeps the event honest, preserves stakeholder trust, and routes the issue to the appropriate coordination mechanism so the team can address it in the next Iteration.
- ✗
Tell the team to quickly integrate the component during the Iteration Review so the stakeholder can see it working.
Why it's wrong here
Asking the team to integrate during the event is unrealistic and turns a review into a working session. It pressures the team to rush, risks introducing defects, and distracts from the event's purpose of inspection and adaptation. The Scrum Master should facilitate transparency and follow-up, not demand last-minute integration.
About these practice questions
This SSM question is part of Courseiva's 385-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam 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.