Chapter 46. How to Have an Effective Sprint Planning
Luis Gonçalves
Any work that your team will perform is planned at the Sprint Planning. The plan brings together the entire Scrum Team and is created through collaboration. Sprint Planning is time-boxed to a maximum of eight hours for a one-month Sprint and probably takes less time for shorter Sprints.
In Scrum, teams plan by picking up work, often stories, from the Product Backlog and committing to execute on that forecast in the upcoming Sprint. It is the Scrum Master’s responsibility to make sure that the event takes place and that the attendants understand the time box and the purpose of the event.
The objective of Sprint Planning is to organize the work and select a realistic scope for the Sprint.
Attendees of the Sprint Planning meeting include:
The Product Owner
The Scrum Master (who acts as a facilitator)
All other team members
Teams agree on the amount of work they can pull from the Product Backlog. Upon an agreement over this forecast, they define the Sprint Goal(s) together with the Product Owner.
The main outcomes of the event are:
The Sprint Backlog, consisting of the stories with acceptance criteria that the team will be committed to in the next sprint
The Sprint Goal
A team agreement to do anything possible to achieve the goal
Some small considerations can be very helpful in increasing the effectiveness ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access