What happens when a Sprint is cancelled? Select three outcomes.

When a Sprint is cancelled, there are specific outcomes that typically occur as part of the Scrum framework. One of the key outcomes is that completed and "Done" Product Backlog items are reviewed. This review is important because it allows the Scrum Team and stakeholders to assess work that has been completed, gather feedback, and adjust the product's direction if necessary.

During the cancellation of a Sprint, the Scrum Team will often take the opportunity to inspect the work that has been completed. This helps ensure that all stakeholders have a clear understanding of what has been achieved and also allows for proper documentation and potential release of the completed work, which prevents any value from being lost.

While other outcomes might be considered, such as discussing the status of incomplete items or re-estimating them, those aren't the primary focus that typically happens when a Sprint is cancelled. Instead, the priority is to evaluate and reflect on the work that has been successfully completed. Additionally, the Sprint Review is generally not conducted unless there is value in receiving feedback on the completed work.

Thus, the rationale behind selecting this outcome underlines the importance of maintaining transparency and fostering discussion about the completed work, enhancing collaboration among the team and stakeholders.