Ace the 2026 CSPO Challenge – Unleash Your Scrum Mastery!

The document that must be finalized prior to the end of Sprint Planning is the Sprint Backlog. The Sprint Backlog is a combination of the Product Backlog items selected for the Sprint and the plan for delivering that product increment. During Sprint Planning, the Scrum Team collaborates to ensure that there is a clear understanding of what will be accomplished in the upcoming Sprint.

This document captures the items the team agrees to work on and the tasks needed to complete these items, thus guiding the development work through the Sprint. By finalizing the Sprint Backlog at the end of Sprint Planning, the team establishes their commitment and creates a baseline for performance. It also provides transparency and accountability, enabling the team to measure progress against the planned work.

In contrast, the other documents mentioned (Sprint Review, Product Backlog, and Sprint Retrospective) serve different purposes and are not required to be finalized during Sprint Planning. The Product Backlog is a living document that can be updated continually, and the Sprint Review and Sprint Retrospective occur at the end of a Sprint, focusing on reviewing work and reflecting on the Sprint process, respectively.