Daily Scrum

Correct Answer: Explain that the Daily Scrum is for the development team to synchronize their work and plan for the next 24 hours, and offer to coach him on its purpose and structure.

The correct answer emphasizes the purpose of the Daily Scrum as a self-organizing event for the development team to coordinate their work, not a status reporting session to the Scrum Master. The wrong answers diverge from Scrum principles: the first suggests unnecessary documentation, the second misrepresents the Scrum Master's role and undermines team self-organization, and the third proposes adding events not prescribed by Scrum, potentially leading to decreased agility and increased overhead.

Correct Answer: Have a one-on-one conversation to understand their concerns and encourage them to share concise updates

Having a one-on-one conversation with the team member who remains silent during the Daily Scrum is the best approach. This allows the Scrum Master to understand the individual's concerns and encourage them to share concise updates in a supportive manner. Calling out the team member during the meeting may make them feel uncomfortable and less likely to participate. Suggesting written updates may not address the underlying issue and could hinder the team's direct communication. While discussing the importance of participation with the entire team is valuable, it may not provide the personalized support the individual needs. By having a private discussion, the Scrum Master can help the team member feel more confident and engaged in the Daily Scrum.

Correct Answer: Talk privately with the team member about the importance of openness and eagerness to adapt, and provide feedback on the observed behavior.

The best course of action when a team member consistently gets defensive during feedback sessions is to talk privately with that individual, and stress the significance of openness and willingness to adapt. It's crucial to provide feedback on the behavior that was observed because it can be a helpful way for the individual to understand how their actions are perceived and the impact it has on the team dynamic. Mentioning this in a private setting helps prevent the person from getting publicly embarrassed or defensive and promotes a positive and constructive conversation. The other answers are less effective. 'Ignoring the situation, hoping it improves over time' is not proactive and won't directly address and resolve the issue. Calling the person out publicly during the daily scrum could create hostility or embarrassment and doesn't allow for a productive and open conversation. Ultimately, it's the role of the Scrum Master to ensure the team is working collaboratively, and simply asking the person to leave the team if they do not change their behavior shouldn't be the first course of action; problems should be addressed and solved as a team first.