Also called: sprint demo.
Italic text is guidance. Delete it as you fill each section in.
| Date | YYYY-MM-DD |
| Sprint Goal | Copied from the Sprint Backlog. |
| Attended | Team plus which stakeholders. Note who was invited and did not come. |
Record the two things that only happened in this room: what stakeholders said, and what changed as a result. Everything else is already in the tracker.
The Guide calls the Sprint Review "a working session" and says the team "should avoid limiting it to a presentation". Notes that list what was demonstrated document the half of the meeting that mattered least.
Yes, partly, or no, then one or two sentences on why.
Answer against the Goal, not the item list. Finishing every item and missing the Goal is a real outcome and worth recording. So is achieving the Goal with two items dropped, which is the framework working rather than a failure.
One line per item, in terms of what someone can now do. Not a walkthrough.
Only work meeting the Definition of Done belongs here. The Guide is explicit that an item which does not meet it "cannot be released or even presented at the Sprint Review".
- ...
The most valuable section, and the one that gets cut when notes are written in a hurry.
Record reactions with attribution, including the ones that were inconvenient. Separate what was observed from what was requested: "three of them looked for export in the wrong menu" is evidence, "they asked for a bigger button" is a proposed solution.
| Who | What they said or did | What it tells us |
|---|---|---|
Decisions and backlog changes coming out of the session, with owners.
The Guide says attendees "collaborate on what to do next" and the Product Backlog "may also be adjusted to meet new opportunities". If nothing changed, write that. A review that never changes anything is a review whose stakeholders have stopped engaging, and noticing that is worth more than the notes.
| Change | Owner |
|---|---|
Anything the team told stakeholders that affects their plans: progress towards the Product Goal, a shift in the market, a dependency that slipped, a budget or timeline change.
Keep it short. This is the part people copy into their own updates, so make it copyable.
Delete this section too.
There is no sign-off, and adding one costs you something real. Scrum has no Product Owner acceptance step at the review; acceptance is the Definition of Done, applied continuously through the Sprint. A review functioning as an approval gate has reintroduced a stage gate, and the Guide addresses this directly: the Sprint Review "should never be considered a gate to releasing value". If your notes have an approval column, that is where to look first.
Absent stakeholders are the finding. The most common failure of this event is not a bad demonstration; it is an empty room. Record who was invited and did not attend, Sprint after Sprint. That pattern is a conversation the Product Owner needs to have, and it is invisible in any single set of notes.
Timebox: four hours for a one-month Sprint, proportionally less for shorter ones.
Write it during the session, not after. Reconstructed reactions become paraphrases of what the team already believed.
Where this lives: the wiki, linked from the Sprint in the tracker. The audience is wider than the team and includes people who will not open a repository.
sprint-backlog.md. Its Sprint Goal is copied at the top of these notesdefinition-of-done.md. Sets which items are releasable enough to be shown at the reviewproduct-goal.md. Progress toward it is part of the context these notes give stakeholderssprint-retrospective.md. What was learned here feeds that event's gather-data stage