Sprint Planning
The event that kicks off the Sprint by laying out the work to be performed, addressing why, what, and how.
What it means
Sprint Planning is timeboxed to a maximum of eight hours for a one-month Sprint, shorter for shorter Sprints. The whole Scrum Team participates, with the Product Owner ensuring attendees are prepared to discuss the most important backlog items.
The event addresses three topics: why this Sprint is valuable (resulting in the Sprint Goal), what can be done this Sprint (selecting Product Backlog items), and how the chosen work will get done (the initial plan, which becomes the Sprint Backlog).
Common mistakes
Developers select the amount of work realistically achievable, informed by past performance, upcoming capacity, and the Definition of Done, rather than having a scope dictated to them.
Example
A team spends the first hour of Sprint Planning agreeing on the Sprint Goal, then two more hours breaking backlog items into tasks.