SSM Supporting ART Events Practice Question
During the Scrum of Scrums, Team Beta reports they will miss a dependency needed by Team Alpha. As Scrum Master for Team Alpha, what is the most appropriate immediate action?
⚠ Common exam trap
The trap here is jumping to escalation or stopping work instead of first using the Scrum of Scrums to collaboratively replan the dependency.
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
✓
Work with Team Beta's Scrum Master to renegotiate the dependency timing and update the ART's program board.
The Scrum of Scrums is the forum for resolving cross-team dependencies. The Scrum Master should facilitate direct collaboration with the other team's Scrum Master to renegotiate timing and update the program board, keeping the ART's plan transparent. Escalating immediately, halting work, or merely logging the risk without replanning all fail to address the dependency effectively.
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 Team Alpha to stop work on the dependent Feature until Team Beta delivers.
Why it's wrong here
Halting work entirely is a drastic response that may waste capacity and delay the PI. The dependency miss should first be addressed through coordination and replanning, not by idling the team; there may be other work or partial progress possible.
- ✓
Work with Team Beta's Scrum Master to renegotiate the dependency timing and update the ART's program board.
Why this is correct
The Scrum of Scrums exists to surface and address cross-team dependencies. Collaborating with the other Scrum Master to adjust timing and updating the program board keeps the ART's plan current and gives Team Alpha a realistic basis for adjusting their own work.
- ✗
Log the dependency as a risk in the team's backlog and continue with the current plan unchanged.
Why it's wrong here
Simply logging the risk without adjusting the plan leaves Team Alpha exposed to a known miss. The program board and team plan should reflect the new reality; ignoring it until later risks compounding delays and surprises at the next system demo.
- ✗
Escalate to the Release Train Engineer to force Team Beta to reprioritize the dependency.
Why it's wrong here
Escalation may eventually be needed, but the Scrum Master's first move is to facilitate collaboration between teams. Immediately asking the Release Train Engineer to force reprioritization undermines self-management and may not respect Team Beta's own commitments and capacity.
Visual reference
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.