It is a space to share triumphs as well as areas of concern. Retrospective meetings are a dedicated time to dig into current processes and tools. Overall, the emphasis should be on what you have learned and how you can apply those lessons to the next sprint. This practice is essential to the agile philosophy of continuous improvement. During the retrospective, agile development teams discuss what went well, what did not go well, and what you can do to make the next sprint even better. Sprint retrospectives are held after a sprint concludes - usually immediately after the sprint review. Jump ahead to the guide sections that are most useful for you: Try the sprint retrospective template in Aha! Notebooks. This guide also includes downloadable sprint retrospective templates if you would prefer to get started that way. If you use Aha! Develop to manage engineering work, you can also make use of team whiteboards and notes within your account. If you want to get started right away, try the built-in sprint retrospective template in Aha! software.
![retrospective sailboat retrospective sailboat](http://sketchnote.me/wp-content/uploads/2019/06/speedboat-copie.png)
In this guide, you can access retrospective templates to help freshen and direct your discussions. To encourage open and fruitful discussions, many teams rely on creative frameworks guided by visual tools or templates. Sprint retrospectives are most popular among scrum teams, but any agile team can hold retrospective meetings to reflect on other types of work - like recent releases or key projects. Using memorable frameworks like these can help to shape your retrospectives, so it is easier to glean insights into your goals, obstacles, and achievements - and improve future sprints. But if you are part of an agile team, you might be familiar with these terms as techniques for retrospective discussions. Are you picturing adventurous excursions? Possibly.