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.

sg20video_plan.mvizdos.com

sg20_playlist.mvizdos.com

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


WORK WITH MICHAEL VIZDOS

CONSULTING | TRAINING


About the Author: Michael Vizdos

Hi. I sincerely appreciate you reading this article. My name is Michael Vizdos and I’ve had the privilege of working with thousands of people on teams all around the world for the past 30+ years of my professional career.

You can read more about my background or contact me or connect with me / send me a direct message on LinkedIn .

Can you do me a quick favor?

If you found this article helpful, please "right click and share" the following link with your internal team (think slack channels) or out on your favorite social media platform:

Scrum Event: Sprint Planning [2024 Video] by Michael Vizdos.

Do you have some feedback to share with me?

Contact me and let's start a conversation. Really.

Otherwise... Keep learning more by clicking through the links to my other articles below. Thank you!



Previous
Previous

Scrum Event: The Daily Scrum [ 2024 Video]

Next
Next

Scrum Event: The Sprint In Scrum [Video]