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.

• ✓

  Coach the team to self-facilitate the stand-up, with members pulling the next speaker rather than reporting to the Scrum Master.

  Why this is correct

  The Daily Stand-up exists for the team to inspect progress toward the Iteration Goals and adapt its plan. When members report to the Scrum Master, ownership has shifted away from the team. Coaching them to self-facilitate and pull the next speaker restores peer-to-peer coordination and reinforces self-management, which is a core Scrum Master responsibility in SAFe. This action directly addresses the observed behavior without removing the event.

• ✗

  Extend the Daily Stand-up to 30 minutes so each member has time to give a complete status report.

  Why it's wrong here

  Extending the timebox validates the status-report anti-pattern instead of correcting it. The Daily Stand-up is intentionally brief to encourage focused coordination; longer meetings tend to drift into problem-solving that should happen afterward. The issue is not insufficient time but the team's orientation toward reporting upward. A longer meeting would make the dysfunction more entrenched and consume more of the team's working time.

• ✗

  Ask the Product Owner to attend and lead the Daily Stand-up so the team stays focused on priority work.

  Why it's wrong here

  The Product Owner's presence can be useful when the team needs clarification on priorities, but assigning the Product Owner to lead the stand-up reinforces the same dependency problem the Scrum Master is trying to solve. The event belongs to the developers, and leadership from outside the team undermines self-management. This option also risks turning the stand-up into a prioritization meeting rather than a daily re-planning event.

• ✗

  Cancel the Daily Stand-up and replace it with a written status update in the team's chat channel.

  Why it's wrong here

  Cancelling the Daily Stand-up removes the daily inspect-and-adapt cycle that SAFe relies on for team self-management and flow. Written updates may improve documentation but do not allow the team to re-plan the day's work collaboratively. The scenario calls for coaching the team back to the event's purpose, not eliminating a core Scrum event. This option also contradicts SAFe's guidance that teams own their events and use them to coordinate daily.