Sprint Planning and Backlog Refinement
10%
Refinement Budget
Typical share of sprint capacity on backlog refinement
2
Planning Outputs
Sprint Goal and Sprint Backlog
2
Definitions
Definition of Ready and Definition of Done
two gates · stories must pass both to earn the badge
Story Pipeline · Ready → Done
how to read this
- › Stories start life as fuzzy ideas in the product backlog.
- › Refinement (ongoing, not a ceremony) shapes them — sizing, clarifying, splitting large stories, adding acceptance criteria.
- › To enter Sprint Planning a story must pass the DoR gate — the Definition of Ready. If it fails, it stays in the backlog.
- › Sprint Planning picks stories that fit capacity and defines a Sprint Goal — the anchor for the whole sprint.
- › To leave the sprint complete, stories pass the DoD gate — tested, documented, shippable. Partial = not done.
Exam Traps
Refinement is ongoing, not a Scrum event
Backlog refinement happens continuously. It is not one of the five Scrum events.
Sprint Goal is the anchor
Sprint Planning produces a goal, not just a list of stories. The goal guides reprioritization if the sprint faces obstacles.
Definition of Ready vs Done
DoR is a story ready to enter a sprint. DoD is a story ready to ship. Both exist. The exam swaps them.
Refine as you go
Do not save refinement for a big meeting. Do a little every sprint.
Not a Scrum event
Backlog refinement is an activity, not a ceremony. Do not treat it as one.
Sprint Planning is setting the menu for the week. Pick dishes that fit the time and ingredients you have.
Refinement is chopping vegetables ahead of time so cooking is fast when it matters.
DoR is ingredients in the fridge, knife sharpened. DoD is the meal plated and served.
Ready to test your PMP knowledge?
1,800 practice questions written by certified professionals.
Start Practicing PMP