Summary

Sprint Planning is a crucial Scrum event where the Scrum Team collaborates to define the work for the upcoming Sprint, ensuring alignment with the Product Goal and the creation of valuable Increments.

Abstract

Sprint Planning serves as the starting point for a Sprint in Scrum, during which the Scrum Team collectively determines the most significant items from the Product Backlog to tackle. This event is characterized by the Developers' active participation in planning the work necessary to achieve the Sprint Goal, rather than being directed by managers. The Product Owner plays a pivotal role in preparing the team for discussion and ensuring that the work aligns with the Product Goal. The Developers are responsible for sizing the work and adhering to the Definition of Done. The Sprint Backlog, which is a dynamic plan owned by the Developers, is created and continuously updated throughout the Sprint to reflect the current state of planned work. The Scrum Team uses past performance, upcoming capacity, and the Definition of Done to inform their planning process. The Daily Scrum serves as a checkpoint for progress and allows for the adaptation of the Sprint Backlog as needed. Sprint Planning is time-boxed to a maximum of 8 hours for a one-month Sprint, ensuring efficiency and focus.

Opinions

The Scrum Guide emphasizes that Sprint Planning is a collaborative effort by the entire Scrum Team, not just the Developers or the Product Owner.
The Developers have the autonomy to plan their work and are encouraged to decompose Product Backlog items into smaller, manageable tasks that can be completed within a day.
The Sprint Backlog is exclusively managed by the Developers, giving them control over how they achieve the Sprint Goal.
The value and utility of the product are communicated through the Sprint Goal, which is a collective effort to define and must be established before the end of Sprint Planning.
Regular adaptation of the Sprint Backlog is encouraged, with the Daily Scrum being a key event for inspecting progress and making necessary adjustments to the planned work.
The article series "Decoding Scrum Guide 2020" aims to provide insights into various aspects of Scrum, including the roles, events, and artifacts, with the goal of enhancing understanding and application of the Scrum framework.

Why do we need Sprint Planning?

Why do we need Sprint Planning?

Sprint Planning is an opportunity for the Scrum team to come together and discuss the next phase of work.

Sprint Planning initiates the Sprint itself; the outcome of the planning session is the work to be performed for the Sprint by the Developer’s. This resulting plan is created by the collaborative work of the entire Scrum Team and not by Manager’s.

Before the Planning session.

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. (Scrum Guide Page 8)

Who plans the work?

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. (Scrum Guide Page 8)

The Sprint Backlog is a plan by and for the Developers. It is a highly visible, real-time picture of the work that the Developers plan to accomplish during the Sprint in order to achieve the Sprint Goal. (Scrum Guide Page 11)

Did you know:

The Sprint Backlog is a plan by and for the Developers.

Who decide how big or small the work is?

The Developers who will be doing the work are responsible for the sizing. This is often done by decomposing Product Backlog items into smaller work items of one day or less. (Scrum Guide Page 8)

Did you know:

No one else tells Developers how to turn Product Backlog items into Increments of value.

How do you know your work is 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. (Scrum Guide Page 8)

What are the 3 things Developers should know before Planning?

· Their past performance

· Their upcoming capacity, and

· Their Definition of Done

How do you adjust the planned work?

The purpose of the Daily Scrum is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary, adjusting the upcoming planned work. (Scrum Guide Page 9)

The Daily Scrum is not the only time Developers are allowed to adjust their plan. They often meet throughout the day for more detailed discussions about adapting or re-planning the rest of the Sprint’s work. (Scrum Guide Page 9)

Did you know: