Getting new sprint retrospective ideas will not alone fix your agile retros. It stops sprint retros from following same format every time to avoid boredom but every agile retrospective should have a purpose and adjusted based on:
- Stage of team development
- Project lifecycle management
- Level of psychological safety
- Recent activity or event team experienced
In Agile ways of working, the retrospective meeting provides the team an opportunity to reflect on their performance and identify areas for growth. While the format of the retrospective can vary, the essence of fostering team cohesion remains.
It is where the team gets to reflect on how they are performing and the opportunity for them to grow.
That said I firmly believe a high performing team is team who constantly delivers wins. Retrospective is a time to reflect on what went well but could be better. Constant small improvements is the agile way.
To do this the team need psychological safety in place to challenge and share. It is where people start feeling more like a team. Tuckman defined the 4 stages of a team are forming, norming, storming, and performing which helps understand why a team is behaving in such a way and requires different approaches.
Psychological Safety in Team Retrospectives
Understanding psychological safety is vital. Research, including Google’s Project Aristotle emphasizes that team members must feel safe to take interpersonal risks—such as admitting mistakes or pitching new ideas—without fear of punishment or ridicule. This shared belief is the foundation upon which effective retrospectives are built.
Discovered through Google’s landmark “Project Aristotle,” psychological safety is the #1 most critical factor for high-performing teams.
What differs from the general process is what I try to think about is how can I help them become a high performing team inspired by The 5 Dysfunctions Of A Team | Teamwork |The Table Group.
Some questions I might ask myself when retro planning:
- What problems are team having ie. friction points
- What is current team mood ie. stressed, celebratory
- What would help team right now ie. safe space to rant, geek out together
- When was last time we held retro – want avoid retro fatigue
- Any unfinished threads from previous retros or meetings
Then the last piece of my retrospective secret sauce is to avoid plain jane simple format. I try to use a theme like a movie/tv show or clever design thinking ones like the sailboat, 3 pigs and etc. When working with teams keeping it fresh works a treat.
To avoid constantly creating these I have created a collection I can copy paste. All I do is take the picture and put it on a virtual whiteboard like confluence, miro, mural etc. Final tip is use a timer to keep on track.
Quick-Reference: Which Sprint Retrospective Idea to Use, By Situation
- New Teams: 4Ls, Hopes & Fears
- Rebuilding Trust: Team Check-in, Premortems
- Recurring Problems: Backcasting, Sailboat
- Before Big Release: Mario Kart, Home Alone
- Quarterly Reflection: Impact Reflection, Shared Understanding Workshop
By organizing retrospectives with these approaches and adhering to psychological safety principles, teams can effectively utilize the retrospective process for continuous improvement and foster a supportive team environment.
Team Forming or Norming Retros
For teams that are still forming, consider starting with formats that build connection and trust. These next simple retros are easy and friendly retro from Agile Meeting Templates | Parabol
I like using these when don’t want to do too much digging and unlock conflict but focus on some positives while also taking risks into consideration.
Hopes & Fears Retro
4Ls – Liked, Learned, Lack, Longed
Top tip: Copy / paste below image into whiteboard and then put 4 rectangles and bring image to front and match colours. People just add post-its to the rectangles.
Rebuilding Trust
When trust is low within a team, it’s important to use retrospectives to foster openness and collaboration. Activities may involve:
- Team Check-in – Focus on psychological safety.
- Premortems – Discuss potential failures openly to build a robust plan and understanding among team members.
Team Check-in
It is the shared belief that team members can take interpersonal risks—such as admitting mistakes, asking questions, or pitching wild ideas—without fear of punishment, ridicule, or humiliation.
Delivery Problems Retro
When the team faces ongoing issues in delivery, retrospectives can be tailored to identify and address these challenges effectively. Suggested activities include:
Sailboat Retrospective
Use the sailboat metaphor to identify what anchors the team down versus what propels them forward.
Leading up to significant milestones, retrospectives should focus on preparation and alignment. You can implement:
Mario Kart – Bananas, Power Up, Worries, Wish and Actions
3 Little Pigs – Straw, Timber or Brick House
Retros for Quarterly Reflection
For broader reflections, especially as part of quarterly reviews, retrospectives can explore long-term strategies. Techniques might include:
I got inspired by Unlocking the Potential of Teams with People-Centered Retrospectives | Easy Agile especially tracking it over time is really important to see trends.
Shared Understanding Retro
After multiple sessions, collect insights to solidify understanding among team members.
The team were participating in a 3day workshop with a bunch of pilot sites and the wider program team. We held a retro on third day to ensure we have a shared understanding from the 3 days and could use it as a springboard for future interactions within the program.
This image from Chen Chen Building a high performance team with retrospectives | by Chen Chen | Ingeniously Simple | Medium really sums up how a project where everybody has different perspective based on their viewpoint.
I wanted to improve Impact from (Understand team effectiveness)
- Co-create a clear vision that reinforces how each team member’s work directly contributes to the team’s and broader organization’s goals.
- Reflect on the work you’re doing and how it impacts users or clients and the organization.
- Adopt a user-centered evaluation method and focus on the user.
Ultimately, while the retro format can provide structure, the true value lies in the actions and follow-ups that arise from the meeting. High-performing teams use the insights gathered during retrospectives to shape their future approach.
High-Performing Team Retro Rotation
To keep retrospectives engaging and effective, high-performing teams regularly rotate their formats. They experiment with different themes and methods like:
The Marvel Retro – Our Super Powers
Use superhero themes to examine strengths and weaknesses.
One of my favourites the Marvel retro where I tool Supercharge Your Sprint Retrospectives: A Marvel-Inspired Guide for Productivity and Growth — The Visual Facilitator and expanded out the boxes. Add your own prompts if you want.
As Stevenson says “framing our retrospective in terms of our favorite superheroes can help us approach our performance with a fresh perspective and identify new areas for growth and improvement”. Check out all his retros here: Retrospectives — Blog — The Visual Facilitator
Minions – Working, Not Working, Improve, Acton
