SSM Supporting Team Events Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Institute a strict 15-minute timebox and cut off any discussion that goes beyond status updates.

  Why it's wrong here

  This fails because the Scrum Master is not the team's timekeeper or enforcer. Imposing a hard stop without team agreement undermines self-management and may prevent necessary collaboration. While timeboxing is a useful practice, the team should decide how to enforce it. The Scrum Master's role is to teach and facilitate, not to police the event, and the team must own the working agreement.

• ✗

  Escalate the issue to the Release Train Engineer and ask them to attend and enforce the timebox.

  Why it's wrong here

  This fails because escalation is not warranted for an internal team event issue that the team can resolve. Involving the Release Train Engineer to enforce the timebox would disempower the team and bypass their ability to self-manage. The Scrum Master should first coach the team to address the problem themselves, only escalating if there are impediments beyond the team's control.

• ✓

  Ask the team what purpose the Daily Stand-up serves and facilitate a discussion on how to keep it focused on progress toward the Iteration Goals.

  Why this is correct

  This is correct because the Scrum Master should coach the team to self-manage by helping them reconnect the Daily Stand-up to its purpose: inspecting progress toward the Iteration Goals and adapting the plan. By asking questions rather than imposing rules, the Scrum Master enables the team to own the solution, which aligns with SAFe's principle of decentralized decision-making and the Scrum Master's role as a servant-leader and coach.

• ✗

  Recommend that the team replace the Daily Stand-up with a written status report to save time.

  Why it's wrong here

  This is wrong because the Daily Stand-up is a core team event in SAFe and cannot be replaced by a written report. Its value lies in synchronous inspection and adaptation, not just information sharing. Eliminating the event would remove the team's daily opportunity to synchronize and adjust their plan, which is essential for maintaining alignment and flow within the Iteration.