SSM Defining the Scrum Master / Team Coach Role 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.

• ✗

  To provide a detailed status report to the Product Owner and the Scrum Master.

  Why it's wrong here

  The Team Sync is not a status meeting for leadership. It is a coordination event for the team members to align on their daily work. Using it as a status report often leads to long, unproductive meetings that don't help the team manage their flow or identify blockers.

• ✓

  To allow the team to synchronize their work and identify any new impediments.

  Why this is correct

  Synchronization is the core of the Team Sync. By sharing progress and identifying blockers daily, the team can adjust their plan in real-time. This ensures that the team remains focused on the Iteration Goal and that any issues are raised and addressed before they become major delays.

• ✗

  To assign new tasks to team members based on their current progress and skill sets.

  Why it's wrong here

  In an Agile team, members pull work from the backlog rather than having it assigned by the Scrum Master. Facilitating the sync involves helping the team manage this self-organization, not acting as a manager who distributes tasks to individuals, which would undermine team autonomy.

• ✗

  To review the technical design of the current Story to ensure it meets the definition of done.

  Why it's wrong here

  Technical design reviews should happen during the work process or in specific technical sessions, not during the Team Sync. The sync is meant to be a short, time-boxed event (15 minutes), and deep technical discussions will cause the meeting to exceed its limit and lose its focus.