Sprint Planning opens the Sprint. The whole Scrum Team collaborates on the plan, and the Product Owner ensures attendees are prepared to discuss the most important Product Backlog items and how they map to the Product Goal. The Scrum Team may invite others to provide advice.
Topic One, why is this Sprint valuable?
The Product Owner proposes how the product could increase its value and utility in the current Sprint. The whole Scrum Team then collaborates to define a Sprint Goal that communicates why the Sprint is valuable to stakeholders. The Sprint Goal must be finalised before Sprint Planning ends.
Topic Two, what can be Done this Sprint?
In discussion with the Product Owner, the Developers select items from the Product Backlog to include in the Sprint. The Scrum Team may refine these items during the process, which increases understanding and confidence. Selecting how much can be completed is often challenging; the more the Developers know about their past performance, upcoming capacity and Definition of Done, the more confident they will be in their forecast.
Topic Three, how will the chosen work get done?
For each selected item, the Developers plan the work needed to create an Increment that meets the Definition of Done. This is often done by decomposing items into smaller work items of one day or less. How this is done is at the sole discretion of the Developers; no one else tells them how to turn Product Backlog items into Increments of value.
The output
The Sprint Goal, the Product Backlog items selected for the Sprint, and the plan for delivering them are together referred to as the Sprint Backlog.