Sprint planning – a Scrum event: Video from the Scrum Guide 2020.

The video “Scrum Event: Sprint Planning” is based on the official 2020 version of the Scrum Guide by Ken Schwaber and Jeff Sutherland.

Listen to the free Scrum Guide audiobook at https://scrumguide.mvizdos.com or watch the digital interactive online version of the latest edition of the Scrum Guide at https://www.InteractiveScrumGuide.com.

To learn more about implementing Scrum in practice and how to be successful with Agile, visit https://www.ImplementingScrum.com, home of the classic Scrum cartoons “Chicken and Pig” by Michael Vizdos.

Subscribe to FREE weekly Saturday morning emails on Scrum Implementation from Michael Vizdos – including the classic Scrum Chicken and Pig cartoons – at https://subscribe.mvizdos.com.

Learn more about Michael Vizdos at https://www.michaelvizdos.com. He is available to provide consulting, training and mentoring to you, your team and your organization worldwide.

Focus. #deliver

=======

Scrum Event: Sprint planning as defined in the official Scrum Guide 2020

Sprint planning

Sprint planning kicks off the sprint by determining the work to be done for the sprint. The resulting plan is created through collaboration across the entire Scrum Team.

The Product Owner ensures that participants are prepared to discuss the key items of the Product Backlog and how they relate to the Product Goal. The Scrum Team may also invite other people to the Sprint Planning to provide advice.

Sprint planning covers the following topics:

Topic One: Why is this sprint valuable?

The Product Owner proposes how to increase the value and utility of the product in the current Sprint. The entire Scrum Team then works together to define a Sprint Goal that communicates to stakeholders why the Sprint is valuable. The Sprint Goal must be set before the end of Sprint Planning.

Topic two: What can be done in this sprint?

Through discussions with the Product Owner, developers select items from the Product Backlog to include in the current Sprint. The Scrum Team can refine these items during this process, increasing understanding and trust.

Estimating how much can be done within a sprint can be challenging, but the more developers know about their past performance, their future capacity, and their definition of “done,” the more confident they can be in making their sprint forecasts.

Topic Three: How is the chosen work done?

For each selected Product Backlog item, developers plan the work necessary to create an increment that meets the Definition of Done. This is often done by breaking 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 value increments.

The Sprint Goal, the Product Backlog Items selected for the Sprint, and the plan for their delivery are collectively referred to as the Sprint Backlog.

Sprint planning is limited to a maximum of eight hours for a one-month sprint. For shorter sprints, the event is usually shorter.

00:00 Sprint Planning Event from the Interactive Scrum Guide
00:22 Sprint Planning Event
00:55 Sprint planning – three topics
01:12 Sprint Planning Topic 1 – Why is this sprint valuable?
01:38 Sprint Planning Topic 2 – What can be done in this sprint?
02:14 Sprint Planning Topic 3 – How will the selected work be accomplished in this sprint?
02:55 Sprint planning is limited to 8 hours or less for a one-month sprint
03:05 Information about the official interactive Scrum Guide
03:18 Learn more about Michael Vizdos, curator of the Interactive Scrum Guide

Please take the opportunity to connect with your friends and family and share this video with them if you find it useful.