Memory hook: Product Goal, Sprint Goal, Definition of Done.
Must remember
The Product Backlog is the evolving ordered source of product work; its commitment is the Product Goal. The Sprint Backlog combines the Sprint Goal, selected work and delivery plan; its commitment is the Sprint Goal. The Increment is usable integrated value; its commitment is the Definition of Done.
The Product Goal gives longer-term direction. The team finishes or abandons it before adopting another. Refinement continuously adds clarity and suitable size to upcoming work; it is not a prescribed formal Scrum event. User stories, story points and a Definition of Ready are optional techniques, not mandatory framework elements.
The Definition of Done establishes shared quality expectations. Work that does not meet it cannot count as part of the Increment. Teams working on one product must agree on and follow the same Definition of Done, meeting organizational minimums. Acceptance criteria for an individual item do not replace product-wide quality requirements.
Multiple Increments can be created/released within a Sprint. Finished work should integrate with prior work. Unfinished items return to the Product Backlog for future consideration; they are not automatically counted as completed or blindly carried into a guaranteed future scope.
Choose under exam pressure
| Requirement | Choice and reason |
|---|---|
| Work coded but required tests fail | It is not Done. |
| Different teams build one product | Shared product direction/backlog and mutually defined Done standard. |
| Need clarity on upcoming work | Continuous refinement. |
Traps
- Acceptance criteria and Definition of Done solve related but different problems.
- Scrum does not require story points.
Active recall
1. Product Backlog commitment?
Product Goal.
2. Sprint Backlog commitment?
Sprint Goal.
3. Increment commitment?
Definition of Done.
4. Can an Increment be released before Review?
Yes, if usable and Done; Review is not a release gate.
5. What happens to unfinished work?
It returns to the Product Backlog for reconsideration, without being counted in the Increment.
Sources
Framework explanation adapted from the 2020 Scrum Guide by Ken Schwaber and Jeff Sutherland, under CC BY-SA 4.0. Changes: condensed wording, original examples, tables and recall scenarios. These five Scrum revision chapters are also offered under CC BY-SA 4.0; this notice does not license unrelated site content or brand artwork.