Scrum Event: Sprint Planning [2024 Video]
Video: Scrum Events - Sprint Planning
This is from the official 2020 Scrum Guide by Ken Schwaber and Jeff Sutherland.
Please share the links above with your friends, teams, leaders, and other stakeholders within your organization. You’ll get bonus points for sharing them on your social networks and internal slack channels.
Scrum Events - Sprint Planning as defined in the official 2020 Scrum Guide
Sprint Planning
Sprint Planning initiates the Sprint by laying out the work to be performed for the Sprint. This resulting plan is created by the collaborative work of the entire Scrum Team.
The Product Owner ensures that attendees are prepared to discuss the most important Product Backlog items and how they map to the Product Goal. The Scrum Team may also invite other people to attend Sprint Planning to provide advice.
Sprint Planning addresses the following topics:
Topic One: Why is this Sprint valuable?
The Product Owner proposes how the product could increase its value and utility in the current Sprint. The whole Scrum Team then collaborates to define a Sprint Goal that communicates why the Sprint is valuable to stakeholders. The Sprint Goal must be finalized prior to the end of Sprint Planning.
Topic Two: What can be Done this Sprint?
Through discussion with the Product Owner, the Developers select items from the Product Backlog to include in the current Sprint. The Scrum Team may refine these items during this process, which increases understanding and confidence.
Selecting how much can be completed within a Sprint may be challenging. However, the more the Developersknow about their past performance, their upcoming capacity, and their Definition of Done, the more confident they will be in their Sprint forecasts.
Topic Three: How will the chosen work get done?
For each selected Product Backlog item, the Developers plan the work necessary to create an Increment that meets the Definition of Done. This is often done by decomposing Product Backlog items into smaller work items of one day or less. How this is done is at the sole discretion of the Developers. No one else tells them how to turn Product Backlog items into Increments of value.
The Sprint Goal, the Product Backlog items selected for the Sprint, plus the plan for delivering them are together referred to as the Sprint Backlog.
Sprint Planning is timeboxed to a maximum of eight hours for a one-month Sprint. For shorter Sprints, the event is usually shorter.
References and Additional Learning Resources
View the “Scrum Events - Sprint Planning” section in the Interactive Scrum Guide.
Listen to the “Scrum Events: Sprint Planning” from the Scrum Guide Audio Book.
Listen to the official 2020 version of the Scrum Guide Audio Book.
View the official online digital version of the 2020 Scrum at InteractiveScrumGuide.com.
Watch the official 2020 Scrum Guide YouTube Playlist at sg20_playlist.mvizdos.com.
Learn more about Implementing Scrum with Michael Vizdos at ImplementingScrum.com.
Subscribe to your free weekly Saturday morning, emails with the original Scrum Chicken and Pig Cartoons about Implementing Scrum by visiting subscribe.mvizdos.com.
Finally, you can learn more about Michael Vizdos, creator of ImplementingScrum.com, the Scrum Guide Audiobook and the Interactive Scrum Guide at michaelvizdos.com.
Get even more FREE resources to learn about Implementing Scrum at learn.mvizdos.com.