The Sprint Backlog is a plan by and for the Developers. During Sprint Planning, the Developers select Product Backlog Items for the Sprint and create an initial plan for delivering them. This plan, which is the Sprint Backlog, does not need to be complete or exhaustive. It must be detailed enough for the Developers to forecast what they believe can be accomplished to meet the Sprint Goal and to start the work of the Sprint. The Sprint Backlog is emergent and will be refined throughout the Sprint as the Developers learn more about the work needed to achieve the Sprint Goal.

B. The Sprint Backlog is emergent and evolves as more is learned. Requiring 100% of the work to be identified upfront is contrary to Scrum's empirical nature.

C. Understanding design and architecture is part of the work, but the Sprint Backlog's primary purpose is to be an actionable plan for the Developers to achieve the Sprint Goal.

D. The Sprint Backlog is owned and managed by the Developers. Their confidence and understanding are paramount, not the Scrum Master's, who serves as a facilitator.

---

1. Schwaber

K.

& Sutherland

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

Page 9

"Sprint Planning" section: "The Developers select items from the Product Backlog to include in the current Sprint... Through discussion with the Product Owner

the Developers select items from the Product Backlog to include in the current Sprint. The Scrum Team may refine these items during this process

which increases understanding and confidence. Selecting how much can be completed within a Sprint may be challenging. However

the more the Developers know about their past performance

their upcoming capacity

and their Definition of Done

the more confident they will be in their Sprint forecasts."

Page 10

"Sprint Backlog" section: "The Sprint Backlog is a plan by and for the Developers... It is updated throughout the Sprint as more is learned. It should have enough detail that they can inspect their progress in the Daily Scrum."

2. Stray

V.

Sjøberg

D. I.

& Dybå

T. (2016). The daily stand-up meeting: A grounded theory study. Journal of Systems and Software

114

101-124. https://doi.org/10.1016/j.jss.2016.01.004

Section 4.1.1

"Planning the day": This study reinforces that detailed planning is an ongoing

daily activity

not a one-time event in Sprint Planning. The Sprint Backlog created in planning is a starting point

"The team members created a plan for the next 24 hours... This plan was often a refinement of the overall sprint plan." This supports the idea that the initial plan is not exhaustive.