Sprint review template
Run the sprint review: a timed agenda, planned vs done, what was demoed, stakeholder feedback and backlog changes.
Use this templateFree, opens in your browser. No sign-up.
What's on the board
- Agenda (60 min)
- Sprint goal recap 5 min · PO · Demo of done work 25 min · team · Stakeholder feedback 15 min · all · Backlog and release outlook 10 min · PO · Next sprint direction 5 min · all
- Done — demoed
- Pay by invoice · Invoice PDF · Email receipts
- Not done → backlog
- Invoice list filters (3 pts left)
- Stakeholder feedback
- Sales: add PO number field · Finance: show due date on PDF
- Backlog changes
- New: PO number field · 2 · Up: invoice reminders
Table columns: Sprint 14, Planned, Actual.
How to use this template
- Click Use this template. It opens in the Kelvo app as a new board, saved in your browser.
- Double-click any box to change its text. Replace the examples with your own content.
- Add notes fast. Press S for a sticky note in the middle of your view. A sticky is a box like any other: link it, recolour it, resize it.
- Move cards between columns. Drag a sticky into another column; select several with a drag box to move them together.
- Present it. Frames become slides when you present, and the laser pointer helps you walk people through the board.
Good for
- sprint review
- demo
- scrum
- stakeholders
- product owner
- Running a retrospective or planning session
- Making the state of work visible on one board
- Agreeing on what “ready” and “done” mean
Related templates
Definition of Ready & Done
The checklists a story must pass before the team takes it, and before anyone calls it done.
Product backlog
A ranked backlog with type, estimate and readiness, plus backlog health and the next refinement session.
Sprint planning
Sprint goal, team capacity, the stories pulled in, and the risks — everything a sprint planning meeting needs.
Sprint retrospective
What went well, what could be better, and action items with an owner — the standard Scrum retro.
RICE prioritization
Score features by Reach, Impact, Confidence and Effort to rank a backlog with numbers instead of opinions.
MoSCoW prioritization
Split a release's scope into Must, Should, Could and Won't-have-this-time so everyone agrees what ships.