Fun and effective agile retrospectives.
A free online retrospective tool to reflect on your work, find topics, and grow as a team.
Funny retro templates
Explore our retro templates to find ideas for your next scrum retrospective or team reflection.
No login required
Invite the participants with a secure link. They do not need to login on teammeter to join the retro.
Fun ice breakers
Get to know each other better, increase your creativity and have fun with a big choice of retro ice-breakers.
Sometimes your team does not see every problem. Enlarge your team’s perspective by including questions from an health check to gather anonymously data about happiness, team dynamics and agile practices.
Facilitating excellent retrospectives requires a lot of experience. Our retro assistant helps the moderator and guide the participants in each step to have the best possible outcome.
Collaborative and interactive
Easily group topics into clusters with drag & drop. Vote for the most important topics and sort them automatically.
Vote for the actions for improvement and export them to your work management software (for instance Jira).
Request feedback from the participants with a ROTI voting (Return On Time Invested) to improve for next retro.
Would you like to try it out?
What is an retrospective meeting in agile?
An Agile retrospective is a recurring meeting in Agile methodologies where teams reflect on their recent work iteration. It focuses on what went well, what could be improved, and actionable changes for the next iteration. By fostering a culture of continuous improvement, it enables teams to adapt, enhance collaboration, and refine processes. The process includes setting the stage, reviewing data, generating insights, identifying action items, making decisions, and assigning responsibilities. Retrospectives celebrate successes, learn from failures, and encourage open communication. They are vital for optimizing teamwork, boosting efficiency, and delivering higher value.
What are examples of agile retrospectives?
- Start-Stop-Continue: Team members discuss what activities or practices they should start doing, stop doing, and continue doing in the next iteration. This simple format encourages reflection on processes and practices.
- Glad, Sad, Mad: Team members share what they are glad about, what made them sad, and what made them mad during the iteration. This approach focuses on emotions and can uncover issues affecting team morale.
- 4Ls – Liked, Learned, Lacked, Longed For: Participants discuss what they liked about the iteration, what they learned, what was lacking, and what they longed for in terms of improvements or changes.
What are the most important questions in a retrospective?
- What went well during this iteration?
- What could have gone better?
- What were the major achievements or successes?
- What were the biggest challenges or obstacles?
- What did we learn as a team?
How to run an agile retrospective?
Agile retrospectives are run in 5 steps:
- Set the Stage: Create a positive atmosphere and state the retrospective’s purpose.
- Gather Insights: Review the iteration’s events and discuss what worked and what didn’t.
- Identify Actions: Pinpoint actionable improvements to address challenges.
- Prioritize and Assign: Decide on key actions, assign responsibility, and set timelines.
- Reflect and Close: Discuss team dynamics, recap findings, and end on a motivating note for ongoing growth.
What are the difference between teammeter and online whiteboard tools (like Microsoft Whiteboard, Miro or Mural ?)
Retrospectives in teammeter are structured whereas with whiteboard tools you have to guide your team through the whiteboard. Whiteboard are great to experiment new meeting formats but are not the most effective for online retrospectives. Users are sometimes lost on a whiteboard and are loosing time to move cards. Whiteboards are also not optimal to be displayed on mobile phones. Teammeter is optimized for retros and guide you and your team to better outcomes.