- Published
- 7 October 2026
- Last reviewed
- 7 October 2026
Understand what Sprint Planning establishes
The November 2020 Scrum Guide describes Sprint Planning through three topics: why the Sprint is valuable, what can be done, and how the chosen work will get done. The Scrum Team collaborates in this event. The Sprint Goal describes the single objective for the Sprint.
This guide is an RDE learning exercise based on that structure. It is not an additional Scrum rule, an exam or a substitute for reading the Scrum Guide. The example describes a fictional product team improving an appointment service.
Discuss value before selecting a list
The Product Owner proposes how the product could increase its value and usefulness during the Sprint. The Scrum Team then works together on the Sprint Goal. Start by discussing the change in user or business experience that matters.
For the fictional service, a candidate objective is to let an applicant see and confirm an appointment without needing a telephone call. The team should test whether this objective is useful, achievable and coherent. Completing ten tickets alone does not explain the intended value.
Select work with realistic context
Through discussion with the Product Owner, the Developers select Product Backlog items for the Sprint. The Guide identifies past performance, upcoming capacity and the Definition of Done as information that helps the Developers forecast what can be accomplished.
Consider access, unfinished work and dependencies rather than assuming every person is available for every day. Do not turn the forecast into a promise that ignores learning. If important information is missing, discuss how the team will investigate it.
Plan how to deliver the objective
The Developers plan the work needed to create an Increment that meets the Definition of Done. They decide how to do the work. Discuss a practical sequence, testing and collaboration so the selected items form a workable plan.
For the appointment example, the team may need to understand the confirmation journey, implement a small usable change and check it against the Definition of Done. These are illustrative activities, not a prescribed Sprint Backlog format.
Use the goal while adapting the plan
The Sprint Goal provides a shared focus while the detailed work can adapt as the team learns. The Guide states that scope may be clarified and renegotiated with the Product Owner as more is learned, without changes that endanger the Sprint Goal.
Practice with a fictional backlog: write one proposed goal, select a small coherent set of items and explain how the delivery plan supports the objective. Then introduce an unavailable dependency and discuss an adaptation that preserves the goal. Read the full Guide to check the boundaries of the exercise.
Source and practice note
Scrum roles, commitments and event guidance are paraphrased from the November 2020 Scrum Guide by Ken Schwaber and Jeff Sutherland. This resource is an original RDE practice aid. The examples are fictional. Adapt it to your organisation and obtain the appropriate decision authority.
Cover image: AI-generated illustrative scene created specifically for this resource.