When is the Sprint Backlog created?

The Sprint Backlog is a direct output of the Sprint Planning event. According to the Scrum Guide, Sprint Planning initiates the Sprint by laying out the work to be performed. The Scrum Team collaborates to define the Sprint Goal, select Product Backlog Items for the Sprint, and create an actionable plan to deliver the Increment. This resulting plan, which includes the Sprint Goal (the "why"), the selected Product Backlog Items (the "what"), and the plan for delivery (the "how"), is the Sprint Backlog. It is created by and for the Developers to guide their work during the Sprint.

A. The Sprint Backlog is specific to a single Sprint and is created anew for each one, not once at the beginning of a project.
C. The Sprint Backlog is an output of the Sprint Planning meeting; therefore, it cannot be created prior to it.
D. While the Sprint Backlog is a living artifact that is updated by the Developers as more is learned during the Sprint, its initial creation occurs during Sprint Planning. ---

1. Schwaber

K.

& Sutherland

J. (2020). The Scrum Guide. Scrum.org.

Page 8

"Sprint Planning" section: "Sprint Planning initiates the Sprint by laying out the work to be performed for the Sprint. This resulting plan is created by the collaborative work of the entire Scrum Team."

Page 9

"Sprint Backlog" section: "The Sprint Backlog is a plan by and for the Developers. It is a highly visible

real-time picture of the work that the Developers plan to accomplish during the Sprint in order to achieve the Sprint Goal... It is created during the Sprint Planning event."

2. Verwijs

C.

& Russo

D. (2023). A Theory of Scrum. Zenodo. https://doi.org/10.5281/zenodo.10033478

Page 11

Section 3.2.1 "Sprint Planning": "The primary purpose of Sprint Planning is to create a plan for the upcoming Sprint. This plan is captured in an artifact called the Sprint Backlog." This academic source confirms that the Sprint Backlog is the plan created during the Sprint Planning event.