Sprint Review Feedback

Gather actionable feedback on your sprint review process.

Try this retrospective live

What went well?

Identify the positive aspects of the sprint review.

The product demo was well-organized and showed our progress clearly.
Stakeholders gave us useful feedback on the product increment.
We stayed on schedule and covered all the planned topics.
What could be improved?

Where did the sprint review fall short?

The demo environment had some technical glitches that disrupted the flow.
We didn't allocate enough time for stakeholder questions and feedback.
Some team members seemed unprepared or disengaged during the review.
How can we improve?

What will we change for the next sprint review?

Conduct a dry run or rehearsal before the actual sprint review.
Allocate more time for stakeholder Q&A and feedback sessions.
Improve the demo environment setup and testing process.
Additional Feedback

Share any other thoughts or suggestions related to sprint reviews.

Consider inviting external stakeholders or subject matter experts occasionally.
Experiment with different formats or structures for the sprint review.
Incorporate more interactive elements or hands-on demos when possible.

What is the Sprint Review Feedback Retrospective?

A sprint review is where your team shows stakeholders what it built and hears their reaction. Sprint Review Feedback is a short retrospective on that meeting: what went well, what could be improved, how to improve it, and anything else people want to raise. Run it straight after the review, while the demo and the questions are still fresh. The findings tend to be practical: the demo environment broke, there wasn't enough time for stakeholder questions, or the work was shown without the business context people needed. Doing this every few sprints keeps the sprint review worth attending. Stakeholders get a clearer view of progress, and your team gets better feedback on the product increment.

Sprint Review Feedback Format

What went well?

Identify the positive aspects of the sprint review.

Encourage the team to share specific examples of what worked well during the sprint review, such as effective demos, insightful stakeholder feedback, or good time management.

What could be improved?

Where did the sprint review fall short?

Invite the team to share constructive feedback on aspects of the sprint review that didn't go as well as planned, such as technical issues, lack of preparation, or ineffective communication.

How can we improve?

What will we change for the next sprint review?

Ask the team to propose concrete steps or changes that would make sprint reviews more useful, such as better preparation, clearer communication or changes to the format or agenda.

Additional Feedback

Share any other thoughts or suggestions related to sprint reviews.

Open the floor for any additional feedback, ideas, or concerns that haven't been covered in the previous topics. Encourage the team to think creatively and share their perspectives.

When to use this retrospective

  • After each sprint review, to capture feedback and pick one or two improvements.
  • When your team thinks the sprint review could be more useful.
  • Every few sprints, as a regular check on how your scrum events are working.
  • When new team members or stakeholders join the sprint review.

Suggested icebreaker questions

  • If the sprint review was a movie, what genre would it be and why?
  • If you could add one unique element to the sprint review, what would it be?

Want a warm-up your team plays, not just answers out loud? Browse free icebreakers →

Ideas and tips for your retrospective meeting

  • Ask everyone for honest feedback, including the stakeholders who attended.
  • Have a facilitator or note-taker so every piece of feedback gets recorded.
  • Pick the improvements that matter most and act on them before the next review.
  • Share the feedback and actions with the wider team and stakeholders.
  • Note what worked so you keep doing it.
  • Check last time's actions before adding new ones.

Frequently asked questions

What is a sprint review feedback template?
It's a board with four columns (what went well, what could be improved, how to improve, and additional feedback) that you use right after a sprint review. It captures team and stakeholder input on the demo and the product increment.
When should you run a sprint review feedback retrospective?
Run it straight after the sprint review, while the demo, stakeholder questions and reactions are still fresh.
Who should take part in a sprint review feedback session?
The scrum team plus the stakeholders who attended the sprint review. That way you hear from the people building the work and the people judging it.
What's the difference between a sprint review and a sprint retrospective?
The sprint review looks at the product: the team shows the increment to stakeholders and discusses what to do next. The sprint retrospective looks at how the team worked during the sprint, and it comes after the review.
How long does a sprint review feedback session take?
Usually 15–30 minutes, since it covers a single meeting.

Related templates

ESVP Retrospective

Check how bought-in the team is before the retro starts

What Went Well Retrospective

The classic two-column retro: what went well and what didn't

Four Ls Retrospective

Reflect on what your team Liked, Learned, Lacked and Longed for

What? So What? Now What? Retrospective

Go from what happened to what you'll do next.

Ready to run this retrospective?Try this retrospective live