When should the Sprint backlog be created?

The Sprint backlog is a crucial artifact in Scrum that outlines the work planned for a specific Sprint. It is created during the Sprint Planning meeting, which marks the beginning of the Sprint. During this meeting, the Development Team collaborates with the Product Owner to understand the highest priority items from the Product Backlog and to refine and break them down into actionable tasks.

Creating the Sprint backlog during this meeting allows the team to collectively discuss and commit to the work they will complete in the upcoming Sprint. This collaborative process ensures that everyone on the team is aligned on the goals and scope of work, which is essential for effective execution.

The other choices do not align with the Scrum framework's principles and practices. If the Sprint backlog were created before the Sprint Planning meeting, it would not incorporate the latest insights and discussions that help the team commit to the right goals for the Sprint. Creating the backlog at the end of the previous Sprint or during the Sprint Execution phase would also undermine the planning process and limit the team's ability to adapt and respond to new information and changes in priorities. Thus, the timing of creating the Sprint backlog during the Sprint Planning meeting is fundamental to ensuring a shared understanding and successful Sprint execution.