Scrum Daily Standup (Daily Scrum)

Correct Answer: Have a private conversation with the team member to understand if there is an issue and how you can support them.

The correct answer focuses on addressing the specific issue with the individual team member in a confidential and supportive manner, which is often the best initial step for a Scrum Master noticing a problem with a team member's engagement. Wrong answers suggest alternatives that, while related to team dynamics and communication, do not directly address the problem with the specific team member or could be considered less immediate or direct solutions to the observed behavior.

Correct Answer: Introduce a parking lot for topics that need further discussion and encourage the team to focus only on the updates relevant to the Daily Scrum goals.

The correct answer suggests using a parking lot to help manage the time of the Daily Scrum by setting aside off-topic or detailed discussions for later, thus keeping the meeting focused and within the 15-minute time-box. The wrong answers suggest actions that either extend the meeting's duration, focus on tools rather than communication and collaboration, or reduce the interactive aspect of the Daily Scrum, which are not recommended practices for addressing the issue of meetings running long.

Correct Answer: Encourage the development team to focus on collaboration and planning for the next 24 hours, rather than providing status updates.

The primary purpose of the Daily Scrum is for the Development Team to inspect their progress toward the Sprint Goal and to plan the next steps for achieving it. This should be a time for the team to align and update each other, not a status reporting session to the Scrum Master. Encouraging collaboration and planning for the next 24 hours focuses on the core objectives of the Daily Scrum, making it the correct approach. The wrong answers divert from these objectives by suggesting alternatives that either place the Scrum Master in a central role, which is contrary to the self-organizing nature of the team, or by introducing additional meetings or tools that could potentially become a burden and detract from the efficiency and effectiveness of the Daily Scrum.