If a team cannot meet the Sprint goal, what is their next step?

In Scrum, when a team realizes that they cannot meet the Sprint goal, it is crucial to address this situation transparently and collaboratively. Engaging in a discussion during the Sprint Review allows the team to reflect on what occurred during the Sprint. This open communication creates an opportunity to analyze obstacles, understand the reasons behind not meeting the Sprint goal, and gather valuable feedback from stakeholders.

The Sprint Review is a key event where the team presents the work completed, discusses what was achieved, and gathers input on how to improve moving forward. Following this, the Sprint Retrospective provides the team with a dedicated space to delve deeper into insights gained, focusing on how processes and teamwork can be enhanced in future Sprints.

This approach supports the foundational principles of Scrum, emphasizing continuous improvement, accountability, and collective ownership of the Sprint outcomes. By contrasting this with the other options, it's clear that ignoring the goal, assigning blame, or prematurely reviewing the project budget do not foster a constructive environment for learning or improvement, and may lead to a negative team dynamic.