Return to site

SCRUM: Sprint Planning ๐Ÿ”ญ

October 22, 2022

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:

1๏ธโƒฃ 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.

2๏ธโƒฃ 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 Developers know about their past performance, their upcoming capacity, and their Definition of Done, the more confident they will be in their Sprint forecasts ๐Ÿ”ฎ.

3๏ธโƒฃ 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.