Sprint Planning Meeting
Sprint Planning is the event that starts the Sprint. The Scrum Team collaborates to plan the work for the upcoming Sprint, answering three key questions:
- Why is this Sprint valuable? → The team defines a clear Sprint Goal
- What can be done this Sprint? → The Developers select Product Backlog Items(PBIs) they believe can be completed
- How will the work get done? → The Developers create a plan for delivering a usable Increment.
The Product Owner is accountable for ensuring that a well-maintained and refined Product Backlog exists. The better the backlog was refined during the previous Sprint(s), the smoother Sprint Planning will be---allowing the team to focus on setting the Sprint Goal and building a realistic plan.
The selected PBIs must be enough to achieve the Sprint Goal, though the team may include more if they believe it's feasible. The Sprint Goal provides direction and focus, especially when things don't go as planned. It helps guide decisions and trade-offs during the Sprint.
Sprint Planning is timeboxed to a maximum of eight hours for a one-month Sprint. For shorter Sprints, it is usually shorter---but the Scrum Guide does not define an exact duration.
The outcome of Sprint Planning is a clear Sprint Backlog, including the Sprint Goal, the selected work, and a plan for turning that work into a valuable Increment.
