Removing Impediments

Correct Answer: Consult with the Product Owner to prioritize backlog items that do not require additional hardware

The correct action involves working within the Scrum framework to address the impediment without immediately trying to solve the hardware issue directly. Consultation with the Product Owner for backlog prioritization helps focus the team's efforts on achievable tasks, adhering to the principle of maximizing work not done. The wrong answers, while plausible actions for a Scrum Master, do not directly address the immediate need to keep the team productive in the face of hardware shortages without straying from Scrum principles.

Correct Answer: Sophia should privately speak with the team member to understand the situation better, showing empathy and readiness to help, while keeping the matters confidential.

The correct action involves addressing the issue with compassion and confidentiality, which is a key part of the Scrum Master's role in removing impediments and promoting a supportive team environment. The wrong answers, although related to team dynamics and performance, either bypass the personal nature of the problem, lack sensitivity, or could infringe on privacy and trust within the team.

Correct Answer: Engage in a one-on-one conversation with the team member to understand the reasons behind the lateness and collaboratively develop a solution to ensure timely attendance.

The most appropriate action for Amanda, as the Scrum Master, is to engage in a one-on-one conversation with the team member who consistently arrives late to the Daily Scrum. This approach allows Amanda to understand the underlying reasons behind the lateness and work collaboratively with the team member to find a solution that ensures timely attendance. By addressing the issue privately, Amanda demonstrates respect for the individual and avoids publicly embarrassing or singling out the team member in front of the entire team. This approach aligns with the Scrum values of respect, openness, and courage, as it promotes open communication and a supportive team environment. Publicly calling out the team member during the Daily Scrum would be counterproductive and could harm team morale. Waiting until the Sprint Retrospective to address the issue would allow the problem to persist throughout the Sprint, affecting the team's focus and productivity. Escalating the issue to the team member's manager without first attempting to resolve it within the team goes against the principles of self-organization and collaborative problem-solving in Scrum.