SSM Defining the Scrum Master / Team Coach Role Practice Question
Marcus is the Scrum Master / Team Coach for the Identity Agile Team. At the ART's Inspect and Adapt, the team's problem-solving workshop reveals that their Stories frequently fail to meet the Definition of Done because testing is squeezed into the last two days of the Iteration. The developers say they cannot test earlier because the test environment is unstable, and the testers say they cannot plan earlier because Stories arrive late. The team agrees the root cause is a handoff-based workflow. Which action best reflects the Scrum Master / Team Coach role in improving this systemic issue?
⚠ Common exam trap
The trap here is choosing a technically appealing fix such as stabilizing the environment or adding a hardening Iteration, when the Scrum Master / Team Coach role is to coach the team through changing its workflow and quality practices.
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
✓
Coach the team to slice Stories smaller, pair developers and testers earlier, and use the team's working agreements to enforce a shared Definition of Done from the first day of the Iteration.
The Scrum Master / Team Coach helps the team improve its system of work rather than fixing symptoms. The handoff-based workflow is the root cause, so the effective action is to coach changes in how work is sliced, when testers engage, and how the Definition of Done is applied. This keeps ownership with the team and aligns with SAFe's built-in quality and small-batch flow principles. Owning the environment fix, adding a hardening Iteration, or creating a testing gate all leave the root cause intact.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Recommend that the team add a hardening Iteration before the PI System Demo so testing has dedicated time without changing the workflow.
Why it's wrong here
Adding a hardening Iteration institutionalizes the handoff and delays feedback, which is contrary to SAFe's emphasis on built-in quality and continuous integration. It treats the symptom rather than the root cause and adds a non-value-adding timebox. The Scrum Master / Team Coach should help the team improve flow and quality practices, not create a buffer that masks the underlying handoff problem.
- ✗
Take ownership of the test environment stabilization by working with the System Team and report status back to the team each day.
Why it's wrong here
While engaging the System Team is useful, personally owning the technical fix moves the Scrum Master / Team Coach into a delivery role and removes the team from solving its own systemic problem. The role is to coach the team through identifying and addressing the root cause, not to become the single point of accountability for an engineering outcome. This also risks the team disengaging from the improvement.
- ✓
Coach the team to slice Stories smaller, pair developers and testers earlier, and use the team's working agreements to enforce a shared Definition of Done from the first day of the Iteration.
Why this is correct
This addresses the root cause by changing how work flows through the team. Smaller Stories and earlier collaboration reduce batch size and handoffs, while a shared Definition of Done makes quality a whole-team responsibility. As Scrum Master / Team Coach, Marcus facilitates the team's agreement and helps it inspect whether the change improves flow, rather than fixing the environment for them or adding buffers.
- ✗
Ask the Product Owner to stop accepting Stories into the Iteration until the testers confirm they have capacity to test them all.
Why it's wrong here
This creates a testing gate that reinforces the handoff and makes testers a bottleneck rather than integrating quality into the team. It also shifts responsibility for flow to the Product Owner and testers instead of the whole team. The Scrum Master / Team Coach should help the team improve its own working system, not introduce a control point that contradicts SAFe's built-in quality principle.
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.