The Scrum Events

Correct Answer: Collaborate with the Product Owner to reassess and reprioritize the Sprint Backlog items.

In situations where the development team realizes they won't be able to complete all selected items, collaborating with the Product Owner to reassess and reprioritize Sprint Backlog items is the most effective approach. This ensures transparency and maintains the focus on delivering the most valuable work given the current circumstances. Attempting to push the team to work harder, ignoring the issue until the next Daily Scrum, or preemptively splitting and deferring work without a collaborative discussion sidesteps the principles of Scrum, which emphasize teamwork, adaptability, and continuous improvement.

Correct Answer: Collaborate with the Product Owner to assess how the proposed changes affect the Sprint Goal.

The correct approach involves collaboration between the Scrum Team and the Product Owner to understand how changes might affect the Sprint Goal. It's about finding a balance and ensuring that any adjustments support the overall success of the Sprint. Simply accepting changes undermines the team's current commitment, while deferring them until the Sprint Review ignores the possibility that some changes could indeed be relevant and beneficial in the current Sprint. Re-prioritizing the entire Sprint Backlog without a collaborative discussion overstates the effort required and misunderstands the flexibility inherent in Scrum to adapt to changes while maintaining focus on the Sprint Goal.

Correct Answer: Collaborate with the Product Owner to re-negotiate the scope of the Sprint Backlog

In Scrum, when the Development Team realizes they cannot finish the work they forecasted, the most appropriate action is to collaborate with the Product Owner to adjust the scope. This is because the scope of the Sprint is flexible and can be renegotiated between the Development Team and the Product Owner to ensure the most valuable and doable work is completed within the Sprint. Increasing hours, restructuring the team, or assigning more tasks unilaterally do not align with Scrum values and principles, such as self-organization, respect, and focus on delivering valuable product increments.