Sprint Planning initiates the Sprint by laying out the work to be performed. The 2020 Scrum Guide explicitly structures this event around three topics, which directly correspond to this answer. First, the team collaborates on a Sprint Goal, addressing "Why" the Sprint is valuable. Second, the Developers select items from the Product Backlog, determining "What" can be done. Third, the Developers create a plan for delivering the selected items into a Done Increment, which answers "How" the work will get done. This comprehensive approach ensures the team has a clear purpose, a selected set of work, and an actionable plan for the Sprint.

A. Who is on the team and what team member roles will be.

This concerns team formation, which happens outside of Sprint Planning. The Scrum Team is expected to be stable throughout the Sprint.

B. How conditions have changed and how the Product Backlog should evolve.

This describes Product Backlog refinement, a continuous activity, not the specific purpose of the Sprint Planning event itself.

C. What to do and who will do it.

While "what to do" is correct, assigning work to specific individuals ("who will do it") during planning undermines the Developers' self-management.

E. What went wrong in the last Sprint and what to do differently this Sprint.

This is the purpose of the Sprint Retrospective, which is focused on inspecting and adapting the team's processes.

1. Schwaber

K.

& Sutherland

J. (2020). The Scrum Guide. Scrum.org. Page 9. The guide states

"Sprint Planning addresses the following topics: Topic One: Why is this Sprint valuable? ... Topic Two: What can be Done this Sprint? ... Topic Three: How will the chosen work get done?" This directly maps to "Why

" "What

" and "How."

2. Verwijs

C.

& Russo

D. (2023). A Theory of Scrum's Law. In Agile Processes in Software Engineering and Extreme Programming – Workshops (pp. 103-112). Springer

Cham. The authors discuss the purpose of Scrum's events

noting that Sprint Planning is for the Scrum Team to "agree on a Sprint Goal (Why)

select the work to achieve it (What)

and create a plan (How)." (Section 3.1

p. 106).

3. Hohl

P.

Klünder

J.

van Bennekum

A.

et al. (2018). Back to the future: why is agile today not what we practiced 10 years ago and what we should practice in the future. In International Conference on Agile Software Development (pp. 125-133). Springer

Cham. The paper reinforces that Sprint Planning involves selecting backlog items and creating a plan to deliver them

covering the "What" and "How" aspects. The commitment to a Sprint Goal provides the "Why." (Section 3).