Sprint Review Template (Scrum Guide 2020)

Scrum Sprint Review notes: Sprint Goal outcome, Done items, demo order, stakeholder feedback, environment changes, Product Backlog adaptation

Produkt & ProjektKompaktScrum Guide 2020sprint reviewAktualisiert 29.10.2026

Im Editor öffnen.md herunterladen

Anleitung: Use it when the Scrum Team meets stakeholders at the end of a Sprint to inspect the Increment and adapt the Product Backlog. Fill the Sprint Goal outcome and the list of Done items first, then capture feedback and backlog changes in the room. The main pitfall is turning the event into a slide presentation or a release gate instead of a working session.

Vorschau

Sprint Review: [Team name], Sprint [NN]

A Sprint Review is the Scrum event where the Scrum Team and its key stakeholders inspect the outcome of the Sprint and decide what to adapt next. This template follows the Scrum Guide 2020 (the latest revision as of October 2026): the team shows the Increment that meets the Definition of Done, the group discusses progress toward the Product Goal and changes in the environment, and the Product Backlog is adjusted. It is a working session, not a status presentation and not a release gate. Replace every [bracketed] value and every row marked Example.

Document control

Field	Value
Document ID	[REVIEW-TEAM-NN]
Sprint	[NN] (YYYY-MM-DD to YYYY-MM-DD)
Review date and timebox	YYYY-MM-DD, [N] minutes
Product Goal	[The current Product Goal, from the Product Backlog]
Sprint Goal	[One sentence, from Sprint Planning]
Product Owner	[@po]
Facilitator	[@name]
Stakeholders invited	[Names or roles]
Last updated	YYYY-MM-DD

Revision history

Version	Date	Author	Change
1.0	YYYY-MM-DD	[@po]	Notes from the Sprint Review

1. Sprint Goal and outcome

Item	Value
Sprint Goal	Example: Field technicians can view and update today's jobs with no network connection
Goal met	[Yes / Partly / No] Example: Partly
Why	Example: Offline viewing and updates work; conflict handling when two people edit the same job is not Done

2. What is Done

Backlog item	Done (meets DoD)	Shown in demo	Released to users	Evidence
PBI-201 (Example) Cache today's jobs on the device	Yes	Yes	No, behind a flag	[Test report link]
PBI-202 (Example) Edit job status offline and sync later	Yes	Yes	No, behind a flag	[Test report link]
PBI-203 (Example) Resolve edit conflicts on sync	No, returned to backlog	No	No	Two acceptance tests fail

3. Demonstration

Order	What is shown	Presenter	User scenario
1 (Example)	Job list opens with the phone in airplane mode	[@dev-a]	Technician in a basement with no signal
2 (Example)	Status changed offline appears in the dispatcher view after reconnecting	[@dev-b]	Dispatcher checks progress at noon
[N]	[What is shown]	[@name]	[Scenario]

4. Stakeholder feedback

ID	From	Feedback	Proposed response
FB-01 (Example)	[Head of field operations]	Technicians also need the site safety notes offline	New backlog item, refine next Sprint
FB-02 (Example)	[Support lead]	Show the last sync time on screen, support will be asked about it	Add to PBI-202 acceptance criteria
[FB-NN]	[Role]	[Feedback]	[New item / change item / no action, with reason]

5. Environment and Product Backlog changes

Changes in the environment: [Example: the largest customer moves its rollout from March to May, which reduces the urgency of conflict handling]

Change	Backlog item	Reason	Decided by
Added (Example)	PBI-215 Offline site safety notes	FB-01	[@po]
Reordered (Example)	PBI-203 conflict handling stays first	Still needed before any external beta	[@po]
[Added / Removed / Reordered / Split]	[PBI-NNN]	[Reason]	[@po]

Progress toward the Product Goal: [Short assessment, for example the share of goal-related items Done and what remains]

Likely focus of the next Sprint: [Input for Sprint Planning; the Sprint Goal itself is set at Sprint Planning]

Related templates and references

Sprint retrospective, held after this event
Sprint planning, Product backlog and Definition of Done
Release plan and roadmap
User story
Scrum Guide 2020, K. Schwaber and J. Sutherland: https://scrumguides.org/scrum-guide.html (revisions: https://scrumguides.org/revisions.html)

Standard and licence note

Structure aligned with the Sprint Review event of the Scrum Guide 2020 (Schwaber and Sutherland, published under CC BY-SA 4.0). This template names and cites the guide only; it does not copy its text, and all wording here is original. Check the current Scrum Guide at scrumguides.org. Template licence: MIT.