Scrum Review

Correct Answer: Guide the team to collaborate on whether and how to adapt the Sprint Backlog to include emergent work, emphasizing transparency and collective decision-making.

The correct answer is about guiding the team to work together to decide if and how the Sprint Backlog should be adapted, ensuring everyone is on the same page and understands the implications of changes. This is in line with Scrum's values of transparency, inspection, and adaptation. The wrong answers either propose too rigid or too lax approaches that don't foster the collaborative and adaptive environment Scrum aims for. For example, requiring executive approval for changes undermines the self-organizing nature of Scrum teams, while allowing individuals to unilaterally add work detracts from the collaborative decision-making process.

Correct Answer: Highlight the valuable individual features built and facilitate a discussion with the stakeholders and team about how they could be synergised better in future sprints.

In this context, the correct approach as a Scrum Master would be to highlight the valuable individual features built and facilitate a discussion with the stakeholders and team about how they could be synergised better in future sprints. This technique preserves team confidence while maximizing further learning and improvement. Expressing disappointment with the team is not constructive and goes against the principles of Scrum. The role of a Scrum Master isn’t to redesign the Product Backlog, which is a responsibility of the Product Owner, making that option incorrect. Lastly, ignoring the issue instead of addressing it can lead to bigger problems in the future, making the last option a poor choice.

Correct Answer: Remind the Product Owner that any changes needing to be made to the Sprint Backlog during the sprint require a collaborative discussion with the Development Team.

The Scrum framework emphasizes collaboration and flexibility within a team while maintaining certain rules and guidelines. The correct approach is to remind the Product Owner and the Development Team that changes during a sprint are subject to discussion and agreement among the team members, rather than being unilaterally decided by any single member, including the Product Owner. Deferring decisions to stakeholders, extending sprints, or enforcing the Product Owner's requests without team consensus are not practices encouraged by Scrum.