Retrospectives & Demos

An overview of our how we do Retrospectives & Demos. We go into what they are, and a few tips to make them effective.


This meeting is held at the end of a sprint. It is divided into three parts:

  • What worked well?

  • What could be improved?

  • What should the commitment be for the next sprint?


  • Gather everyone’s points: Collect notes from everyone before the meeting. Present all these on a canvas.

  • Everyone should be heard: It’s important to get everyone’s opinion. Ensure the environment is safe to share what they think didn’t work.

  • It’s about improvement: The meeting will help you identify areas that need improvement. List these down and act on them. It will improve the experience your team has working with you.


Each sprint is followed by a demo. All team members and stakeholders are a part of this meeting.


  • Sprint Goal: At the start of the meeting talk about the sprint goal. It will get everyone on the same page.

  • Demo each feature: Demo each feature that was built.

  • Who should demo: It’s usually best if one person does the demo. Typically the technical lead.

  • Feedback: Gather feedback on each feature from all stakeholders.

Last updated