# Retrospectives & Demos ### Retrospectives 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? #### Tips * *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. ### Demos Each sprint is followed by a demo. All team members and stakeholders are a part of this meeting. #### Tips * *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. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://playbook.wednesday.is/project-management-playbook/our-approach/agile-ceremonies/retrospectives-and-demos.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.