360° Review
Agile Retrospectives
Learn how to turn a good team into a great one with continuous improvement practices.
How to start
The Five Phases of a Retrospective
Set the Stage
Greet all attendees, break the ice, and ensure everyone understands the session’s goal.
Gather Data
Review the past work cycle: What went well? What didn’t go as well? What could be better?
Generate Insights
Group similar ideas into topics, let everybody vote to find the most relevant ones.
Decide What to Do
Group similar ideas into topics, let everybody vote to find the most relevant and define action items.
Close the Session
After assigning action items, make a brief abstract of the session and its outcomes. Thank everyone.
Improve your technique
Retrospectives’ Basics
Before going all in, you might want to get solid foundations to prevent any risk.
Retros for Beginners
In these sessions, the team gets together and looks back on past events or situations to achieve continuous improvement.
They're usually celebrated at the end of each sprint.
The whole team, including the Scrum Master, should join the session.
The Business Value
Business Value is vital in product and project management. There is not, however, a single way to measure Business Value. Still, you should add it as a critical parameter to review.
Reviewing the correct KPIs is a good north-star for your sessions.
Conceiving Action Items to address the issues brought up is vital.
The Prime Directive
Gathering your team to discuss how the past work cycle went is excellent, but it can easily turn into a blaming game, potentially hurting your team’s health.
The Prime Directive sets the correct mood for any Retrospective.
It was first coined by expert Norman Kerth in his 2001 book Project Retrospectives: A Handbook for Team's Reviews
Post-Mortems vs. Retrospectives
They might sound similar but be careful not to confuse them: Post-Mortems are not the same as Retrospectives. Each one is driven by a distinct goal and dynamics.
A Post-Mortem analysis focuses on studying the failures encountered after a project has been finished.
Retrospective sessions' purpose is planning ways to increase quality and effectiveness, without requiring the project to be finished.
Become a Pro
Good Practices
Run Retrospectives Easily
We’ll Do The
Heavy Lifting
Simple and highly customizable sessions
Choose between templates or create your own.
Create an anonymous session to boost participation.
Export action items for enhanced follow-up.
Available on
Jira
Confluence
monday
Trello
FAQ
Frequently Asked
What is a Retrospective?
It’s a session held at the end of each sprint or work cycle where a team gathers to review what went well, what didn’t, and what could be improved for the subsequent iterations.
What is the purpose of Retrospectives?
Its main goal is to foster a continuous improvement culture inside a team or organization, delivering more value in less time.
When is a Retrospective meeting held?
Retrospectives are usually performed at the end of each sprint, which traditionally lasts between two and four weeks. You can set a custom frequency to better fit your needs.
How to do Retrospectives with remote team members?
Our Agile Retrospectives app supports remote and asynchronous work. It’s available on Jira, Confluence, monday.com, and Trello, so any team can benefit from its customizable features.