Purpose of the Sprint Planning
The purpose of the Sprint Planning Event is to create a Sprint Goal and an actionable plan for the Sprint. The Sprint Planning Event answers two questions:
- What can be delivered as part of the Product Increment in the upcoming Sprint?
- How will the work needed to deliver the Product Increment be achieved?
The Sprint Planning Event consists of two parts, called ‘topics’. Topic one answers the question ‘What can be done this Sprint’. Topic two answers the question: ‘How will the chosen work get ‘Done’?’
The time-box for Sprint Planning is 8 Hours, for a Sprint of 4 weeks. For shorter Sprints, the time-box is usually shorter.
The participants of the Sprint Planning Event are the Scrum Team members, meaning the Product Owner, Scrum Master and Development Team. The Development Team may invite people outside the Scrum Team if needed, to gain technical or domain advice.
During the Sprint Planning meeting, the following is being Inspected:
- The Product Backlog;
- The Product Increment delivered in the past Sprint;
- The Definition of Done;
- The Development Teams’ past performance (Velocity);
- The Development Teams’ projected capacity for the current Sprint;
During the Sprint Planning meeting, the following is being Adapted:
- Sprint Goal
- Sprint Backlog
In order to help you in getting started with the Sprint Planning Event, I’ve created a ‘Sprint Planning Flowchart’ (see image below). This flowchart offers insights into what a typical Sprint Planning Event would look like.