> For the complete documentation index, see [llms.txt](https://www.designreference.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.designreference.xyz/leadership/meetings/retrospectives.md). # Retrospectives A retro or retrospective meeting is a time for a team to look back on a project or a period of work. They discuss what went well, what could have been better, and what lessons they can learn for future projects. It's a way to improve and learn from past experiences. There are different types of retrospective meetings, each with their own unique structure and focus. However, they are typically held after a project or a sprint in agile environments. In essence, they are a post-sprint meeting to review what went well and what didn't in order to work more effectively going forward. #### Sprint Retrospective This is the most common type of retrospective, held at the end of each sprint in an Agile development process. The team reflects on the past sprint and three basic questions are asked. * What actions would you start? * What actions would you stop? * What actions would you continue? {% embed url="" %} {% embed url="" %} #### Release Retrospective Similar to a sprint retrospective, but focused on a larger release or project milestone. The team reflects on the entire release, identifying successes, failures, and lessons learned. #### Project Retrospective This is a retrospective held at the end of a large project or initiative. The team takes a broader look at the entire project, evaluating its overall success, identifying areas for improvement, and capturing lessons learned for future projects. #### Team Retrospective This retrospective focuses on the team's overall performance and dynamics. The team discusses its strengths, weaknesses, communication patterns, and collaboration habits. The goal is to identify areas for improvement in how the team works together. {% embed url="" %} #### Product Retrospective This retrospective focuses on the product itself. The team discusses the product's features, user experience, and overall value proposition. The goal is to identify areas for improvement in the product and its development process. #### Technical Retrospective This retrospective focuses on the technical aspects of a project or product. The team discusses the code quality, architecture, testing practices, and other technical concerns. The goal is to identify areas for improvement in the team's technical practices. #### Curated Library {% embed url="" %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://www.designreference.xyz/leadership/meetings/retrospectives.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.