Sprint demo meeting template
A sprint demo template that will help you tell a story and excite your stakeholders along the way.
Paweł Łubiarz [Source]
About this template
A sprint demo is more than just a presentation. Rather, it’s an opportunity for stakeholders and the development team to get excited about the progress and future of the product.
Product manager Paweł Łubiarz came up with this template to conduct the perfect sprint review demo. The essence? Tell a meaningful story to stakeholders by walking them through the demo (and how the demo review fits in the timeline). By making the meeting engaging, your stakeholders will get excited about your team’s progress.
Sprint Demo Meeting Agenda
1. Present the sprint goal
What is the goal of the sprint? How do you emphasize during your presentation?
2. Review of what’s done and what hasn’t been done Give a high-level overview of what has been achieved and how it ties into the Sprint planning or previous demos (did you achieve what you said you would last time?)
What was done in the sprint?
What hasn’t been completed yet?
3. Demo the work Tell a story from the particular persona or user role. Stakeholders want to see the value of your product. Try to structure the demo into a series of scenarios or scripts that minimize context switching.
What are the general themes in the work you completed?
How does your work tie into the broader sprint goals?
4. Ask questions and share observations
What can be seen in the demo?
5. Review key metrics
Key Metric 1
Key Metric 2
6. Review the timeline and priorities At the end of each scenario (as well as the demo as a whole), point to the future directions for the work so that the stakeholders know what to expect next time.
Source: Paweł Łubiarz
When to use this template
Whether it’s for quarterly, weekly, or bi-weekly sprint demo meetings, this template creates an important time and space for stakeholders and the development team to “discuss the product increment and receive feedback.”
This template is not just for showcasing demos; it also allows for the development team to reflect internally on their sprint goals by reviewing their progress and deciding what to do in the next sprint.