Retrospective is a meeting held by a project team at the end of a project iteration of its inspect-and-adapt or continuous improvement process. Use `sprint-retrospective` instead for Scrum-specific retrospectives. Do NOT use this tag for questions about postmortems; use the `postmortem` tag instead.
About the retrospective Tag
When applied to software development, Wikipedia defines a retrospective as follows:
The term is also used in software engineering, where a retrospective is a meeting held by a project team at the end of a project or process (often after an iteration) to discuss what was successful about the project or time period covered by that retrospective, what could be improved, and how to incorporate the successes and improvements in future iterations or projects. Retrospective can be done in many different ways.
In agile development, retrospectives play a very important role in iterative and incremental development. At the end of every iteration, a retrospective is held to look for ways to improve the process for the next iteration.
Writing a Good Question About Retrospectives
Ensure your question contains sufficient context to understand how this tag applies to a specific problem you are currently facing. Your question should also contain clear objective, and some examples of what you've tried and why what you've tried hasn't worked for you.
When possible, use the most specific tags possible for your question rather than more general tags, especially if the general tag is a superset. Consider the following tags:
Note that while there is often overlap, related tags aren't necessarily synonyms. Use them when they help clarify the scope or intent of your question.
Suitability for Project Mangement Stack Exchange
To be considered on-topic, each question should provide enough context to allow for a potentially-canonical answer. Open-ended questions, opinion polls, or extended discussion about categories are explicitly off-topic on this site.