SSM Defining the Scrum Master / Team Coach Role Practice Question
During PI Planning, a Scrum Master notices that their team is not identifying any dependencies on other teams, despite working on a complex multi-team Feature. What should the Scrum Master do?
⚠ Common exam trap
Students often think the Scrum Master should go find the dependencies themselves or wait for the Release Train Engineer to point them out during the draft plan review.
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 probing questions about how the team's work interacts with other components of the system.
In SAFe, the Scrum Master plays a critical role during PI Planning by facilitating the identification of dependencies and risks. Cross-team coordination is vital for the success of the Agile Release Train. By prompting the team to look beyond their own backlog, the Scrum Master ensures that the Program Board accurately reflects the reality of the delivery plan.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Contact the Release Train Engineer to have them review the team's plan for missing dependencies.
Why it's wrong here
Relying on the RTE to find dependencies is an escalation that should only happen if the team is stuck. The Scrum Master's first responsibility is to coach the team to identify these dependencies themselves during the planning process to foster ownership and proactive communication.
- ✓
Ask probing questions about how the team's work interacts with other components of the system.
Why this is correct
Asking probing questions is a powerful coaching technique that helps the team think critically about their integration points. This facilitates the discovery of dependencies without the Scrum Master doing the work for them, ensuring the team remains accountable for their own plan and commitments.
- ✗
Wait until the Draft Plan Review to see if other teams identify dependencies on your team.
Why it's wrong here
Waiting for the Draft Plan Review is reactive and can lead to significant rework if dependencies are found late. Effective planning requires proactive identification of dependencies early in the process to allow for negotiation and adjustment before the plan is presented to the stakeholders.
- ✗
Document the lack of dependencies as a 'Risk' on the ROAM board for the train to manage.
Why it's wrong here
A lack of dependencies isn't a risk to be ROAMed; it is often a sign of incomplete planning in a complex environment. The ROAM board is for identified risks that impact the PI, not as a substitute for the fundamental work of identifying how teams must collaborate.
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.