What is Sprint Planning?
Learn About the Sprint Planning Event
As described in the Scrum Guide, the work to be performed in the Sprint is planned at the Sprint Planning. This plan is created by the collaborative work of the entire Scrum Team.
Sprint Planning is time-boxed to a maximum of eight hours for a one-month Sprint. For shorter Sprints, the event is usually shorter. The Scrum Master ensures that the event takes place and that attendants understand its purpose. The Scrum Master teaches the Scrum Team to keep it within the time-box.
Sprint Planning answers the following:
- What can be delivered in the Increment resulting from the upcoming Sprint?
- How will the work needed to deliver the Increment be achieved?
Work is selected from the Product Backlog and pulled into the Sprint Backlog. Now remember that the work in the Sprint Backlog is not a commitment, it is a forecast. The only container of a Sprint is its time box, not the work planned for the Sprint. Learn more about the Sprint Backlog and Product Backlog.
The Sprint Goal is an objective set for the Sprint that can be met through the implementation of Product Backlog. It provides guidance to the Development Team on why it is building the Increment. It is created during the Sprint Planning meeting. The Sprint Goal gives the Development Team some flexibility regarding the functionality implemented within the Sprint. As the Development Team works, it does so with the Sprint Goal always in mind.
In this Scrum Tapas video, Professional Scrum Trainer Don McGreal reviews how he runs a Sprint Planning session with his Scrum Teams. Don focuses on how the Development Team works with the Product Owner to understand what is in the Product Backlog and how they populate the Sprint Backlog.
- Scrum Glossary describes important terms of Scrum.
- Scrum Myth: Sprint Backlog is Fully Build and Assigned in Sprint Planning
- Scrum Myth: There is No Planning in Scrum
- 5 Common Planning Mistakes
- Visit the Scrum Blog and Forums