SSM Introducing Scrum in SAFe 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.

• ✗

  Extend the Stand-up meeting to 30 minutes to cover all details.

  Why it's wrong here

  Extending the meeting to 30 minutes is a direct violation of the Scrum guide and the purpose of a stand-up. It encourages long-winded reporting rather than synchronization. The Scrum Master should focus on improving the efficiency of the meeting, not simply adding more time to it.

• ✗

  Require that all team members send a written report before the meeting.

  Why it's wrong here

  Replacing the Stand-up with written reports eliminates the interactive element of the meeting, which is key to team alignment. The purpose of the Stand-up is to facilitate verbal collaboration. If it is too long, the team should be coached on how to report more concisely, not replaced by text.

• ✓

  Coach the team to keep updates concise and move technical discussions offline.

  Why this is correct

  The Scrum Master's role is to keep the meeting focused. By training the team to recognize when a discussion is getting too detailed, they can prompt the participants to take that topic 'offline' for a separate discussion. This keeps the Stand-up fast and ensures it remains relevant for everyone.

• ✗

  Facilitate the meeting by asking each team member for their current task list.

  Why it's wrong here

  The Stand-up is for the team to sync, not for the Scrum Master to status-check individuals. Focusing on a task list turns the meeting into a reporting exercise toward the Scrum Master, which undermines team self-organization and turns the event into an administrative burden rather than a team collaboration.