TEMPLATES

Retrospective Templates

A retrospective activity is a meeting that takes place at the end of a project to evaluate what went well, what didn't go so well, and what could be improved.

A retro is an essential part of good project management and is often held at the end of sprints in agile teams. Since retrospectives are a simple and easy way to learn, share experiences, provide input and find ways to improve going forward, they can also be used as a regular activity among stakeholders or to reflect on individual projects once they have been completed. This includes identifying the successes and the failures with an aim to reflect on the process and find ways to do things better next time.

Retrospective Examples

 4Ls Retro Template

4Ls Retro Template

From
  • Identify what your team liked, loved, lacked and needed longer for during your project.
  • Gain insights into your previous work and take valuable lessons for the future.
Use This Template
Starfish Retrospective Template

Starfish Retrospective Template

From
  • Break down the previous sprint into what should be done more and what should be done less.
  • Take positive activities into your next projects and identify activities to stop doing and new things to start trying out.
Use This Template
Kanban Retrospective Template

Kanban Retrospective Template

From
  • Simplify your retrospective by evaluating what went well, what didn't and what actions should be taken.
  • Assign tasks to owners to ensure actions are taken over into the next phase of work.
Use This Template
Start Stop Continue Retrospective Template

Start Stop Continue Retrospective Template

From
  • Identify new methods to start, practices to stop and activities to keep doing during your next phase of work.
  • Give each time member the opportunity to share how they feel the next project should be approached.
Use This Template
Timeline Retrospective Template

Timeline Retrospective Template

From
  • Get a detailed overview of how your project progressed over time.
  • Consider what went well and what didn't at different stages of the project and determine what effect they had on the final outcome.
Use This Template

Frequently Asked Questions

What are the 3 retrospective questions?

  1. What went well?
  2. What didn't go well?
  3. What could be improved?

What is the purpose of a retro?

A retrospective is a meeting in which the team reflects on what went well, what challenges they faced, and how they can improve in the future. The primary goal of a retrospective is to identify and remove impediments that are preventing the team from delivering their project or product successfully. The team members will collaborate in an open discussion to identify obstacles and decide on solutions that can be implemented going forward.

How long should a retrospective last?

The rule of thumb is to dedicate at least 30 minutes for each project week. For example, if your project or sprint lasts 2 weeks, aim for an hour-long retrospective. It’s also best to do retros in one sitting if possible so the team can stay focused.