Plan a Sprint around a useful goal with a pickup-booking case, a worked capacity example, selected work, quality and adaptation decisions.
The workbook connects Product Goal, Sprint Goal and Sprint Backlog through one complete planning conversation. It includes capacity assumptions, dependency checks and original scenarios for changes during the Sprint.
Plan around a useful goal
Sprint Planning creates a coherent reason for the work and a credible starting plan. The near-term objective should support a coherent product direction. Planning is easier when important needs and uncertainties are understood. Availability is an input to a forecast, not a promise of perfect productivity.
Three Developers each have 10 working days with 6 planned focus hours, giving 180 hours. Subtract 18 known absence hours and 24 separately planned support hours to obtain 138.
Learn from previous delivery
History is useful when the work and conditions are comparable. The goal should help the team make choices as details change. A coherent goal still needs achievable work and acceptance evidence. Developers decide how to turn selected work into a usable Increment.
Verify the scheduling interface, implement slot selection and reservation behaviour, test capacity changes and confirm the agreed result. The team decides who collaborates on each part.
Make quality explicit
A forecast should include the effort needed to meet the Definition of Done. A known external wait can dominate a short planning horizon. The artifact should show the goal, selected work and a delivery plan. Use one coherent thread from value to the first actions.
Developers plan the interface test, slot-selection behaviour, reservation change and confirmation checks. They make the external access risk and shared quality requirements visible.
Adapt during the Sprint
The plan should change when evidence changes the best next step. A request needs assessment against impact, goal and available options. Planning begins a learning cycle that continues through the Sprint. A plan is useful when the team can explain its purpose and act on it.
Are selected work, capacity, dependencies, uncertainty and quality understood? Do Developers own a feasible starting plan?
Contents
- Plan around a useful goal
- Connect with the Product Goal
- Prepare the candidate work
- Understand the team’s capacity
- Learn from previous delivery
- Draft an outcome-focused Sprint Goal
- Choose a feasible slice
- Create the initial plan
- Make quality explicit
- Check dependencies and uncertainty
- Read the Sprint Backlog
- Work a complete planning example
- Adapt during the Sprint
- Handle a new urgent request
- Use the events for their purposes
- Your Sprint Planning desk check
Using the PDF
Each numbered page contains an explanation, an original worked situation and a practical action. The bookmarks navigate the learning pages. A templates advertisement follows content page 5 and a Coursera Plus advertisement follows content page 15. The entire advertisement image is linked. Promotional links may earn Coursya a commission. A purchase is optional.
Frequently asked questions
Who is this guide for?
Plan a Sprint around a useful goal with a pickup-booking case, a worked capacity example, selected work, quality and adaptation decisions.
How can I practise the ideas?
Follow the running case, work through the page actions and use the PDF bookmarks to revisit a topic. The final learning pages help you apply the decisions to your own project.
What does the download contain?
The PDF contains 19 pages, including 16 numbered learning pages, a cover and two linked advertisements. The book is written in English.


