Agile meetings

Sprint demo meeting template

A sprint demo template that will help you tell a story and excite your stakeholders along the way.

Template author

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?

  • Any feedback?

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.

Run better meetings with Vowel

Connected icon

Prepare

Create an agenda (or use a template!) so everyone is on the same page before the meeting.

People icon

Meet

Vowel has one-click recording and transcription, so you can stay focused on the discussion.

Checkmark icon

Act

End every meeting with shared notes, links, and action items — all in a post-meeting recap.


Related agendas

Back to index

Sprint planning meeting agenda

Introduction and purpose (~5 mins)
  • Introduce team members

  • State the meeting’s purpose

Goal setting (~5 mins)
  • Define goals and objectives

Team capacity and velocity (~10 mins)
  • Determine team capacity

  • Determine team velocity

Sprint backlog (~30 mins)
  • Examine the current backlog of user stories

  • Decide the sprint’s priorities

  • Make sure each team member understands what each user story entails

Wrap-up and action items (~10 mins)
  • Do a brief wrap-up of what the key goals are and what the action plan is.

  • Set clear action items and ensure everyone understands what has to be done

For [name] [role]
  • [ ] Action Item 1

  • [ ] Action Item 2

For [name] [role]
  • [ ] Action item 1

  • [ ] Action item 2

Agile meetings

Sprint planning meeting template

A template that will help you cover all your sprint planning bases efficiently.

Sprint Retro Meeting Agenda

1. Set the stage

Purpose: Focus: Length of meeting: 

  • Create or use a working agreement (spend no more than 15 minutes)

  • Review the improvements or experiments from the past Retrospective

  • Warm-up and do a quick check in (can use an ice-breaker)

2. Gather and share data Start with the hard data: events like changes in the team or milestones, metrics like velocity, throughput, etc. Create a timeline of events from the team’s input. Then ask the team to interpret the data and comment on it.

3. Generate insights What helped the team succeed and what brought them down? Let any team members share their insights, or use a model like “stop-start-continue.” 

4. Decide what to do next After seeing the big picture, let the team group the post-its per topic and vote on the most important ones. Then plan experiments and actions to take in the next sprint.

5. Close the retrospective Gather feedback at the end of the meeting and assign action items. 

Source: Maria Chec

Agile meetings

Featured

Sprint retro meeting template

Bring your team together to reflect in a meaningful way with this sprint retro meeting agenda.