As a psychologist and Scrum Master, I probably have an unusual perspective on Sprint Retrospective ideas. I have a somewhat stronger focus on the "soft" side of continuous improvement. You could also call it the agile mindset.
With that in mind, I’d like to share a few Sprint Retrospective ideas that I personally recommend – and some others I would suggest avoiding. Of course, these are just my own views based on personal experience. But don’t worry: my main goal is simply to help your team walk away feeling that a) it was an exceptionally valuable and engaging retrospective (whether you work with Scrum, Kanban, or even Waterfall), and b) that you’ve defined clear, meaningful action items to move forward with (see also: 10 tips for good retrospective measures).
9 Sprint Retrospective Ideas Evaluated: 5 Winners
In the following table, I will now give you an overview of 9 different ideas for sprint retrospectives, including my personal assessment of how well these retrospective ideas actually work in practice. As you will see, the following sprint retrospective ideas are particularly recommended:
- Battery Retrospective
- Sailboat Retrospective
- Team Morale Health Check Retro
- News magazine Retro
| Sprint retrospective idea | Rating | Context | 
| "What went well" Retro | ❌ Bad | It is often difficult in a social group to say openly what is going "badly" – would not recommend this idea. | 
| "4L Loved Learned Longed" Retro | 👍 Medium | The focus on "learning" and very diverse questions are positive, but there are better retro ideas. | 
| "Mad Sad Glad" Retro | ❌ Bad | Ask yourself this: do you really want to tell your senior colleagues – or even your manager, if they join the retro – what makes you feel "sad" or "mad"? Many team members find this uncomfortable, so I wouldn’t recommend using this format. | 
| Sailboat Retro | ✅ Good | This metaphor makes the retro playful and it psychologically easy to communicate challenges – good retro format! | 
| Team Morale Health Check Retro | ✅🚀 Very good | Several important questions where participants can anonymously indicate their agreement or disagreement – a highly recommended format! | 
| Retro battery | ✅🚀 Very good | A novel retrospective idea with a metaphor that everyone immediately understands and that stimulates creativity – highly recommended retro format! | 
| Starfish Retrospective | 👍 Medium | A nice visual metaphor, but the questions themselves are too direct for my taste, similar to other criticized retro formats. | 
| Mario Kart retrospective | ✅ Good | A novel, playful theme for a retrospective: great for teams who like such nerdy games. | 
| News magazine Retro | ✅ Good | A great metaphor where the questions will put a smile on your team members' faces. | 
I hope that the context is sufficient to justify my agreement or disagreement. Before we look at the sprint retro ideas, let's briefly define together what a retrospective is.
What is a Sprint Retrospective: Definition
To keep it short: At its core, the retrospective is about reflection. Can you imagine an elite team that doesn't regularly reflect on how it can work better together? In the long term, that would be about as successful as a car company that stops focusing on customer needs.
At the end of the typically 2-week Scrum sprint, you have a 30-90-minute meeting with the entire team to answer the questions: What is going well right now and what can we do better? What measures will we try out in the next sprint? However, it is not insignificant how exactly these questions are asked – which brings us to the best sprint retrospective ideas.
The agile Sprint Retro can be moderated by the Scrum Master, Agile Coach, but in practice it is also often moderated by the Engineering Manager, Product Owner or Team Lead (more on: Agile Retrospective). The moderator should observe the 5 phases of a retrospective – although I would recommend organizing the retrospective according to 6 phases (see also: The double-diamond model – 5 phases of a retrospective are not enough). Let's finally get started with the presentation of the specific questions from the 9 ideas for sprint retrospectives.
Ideas & formats for sprint retrospectives 1
The "What Went Well" retrospective 👍
The classic retrospective questions are asked – not particularly creative, but some Scrum teams like it simple (more on: Retrospective in Scrum).
Open Feedback Questions
What went well?
What went not so well?
How can we improve?
Ideas & formats for sprint retrospectives 2
4L's Sprint Retrospective idea 📘
The 4 L's stand for "Liked, Learned, Lacked, Longed for". I like the focus on learning, which is why I don't think the format is bad.
Open Feedback Questions
Like: What did you like?
Learned: What did you learn?
Lacked: What did you lack?
Longed for: What did you long for?
Ideas & formats for sprint retrospectives 3
The Mad Sad Glad retrospective 😯
The "Mad Sad Glad" retrospective idea uses different emotions as the basis for the questions. If you ask me, I would rather not recommend it – I rarely experience sadness or madness during a Scrum Sprint...
Open Feedback Questions
What made you mad? 😤
What made you sad? 😢
What made you glad? 🤩
Ideas & formats for sprint retrospectives 4
The Sailboat Retrospective ⛵️
The sailboat retrospective idea is one of the classics that I can recommend: Everyone will understand the format immediately. However, some teams may find it "childish" – so you should make sure that it suits your agile team.
Open Feedback Questions
⚓️ Your anchor: What holds us back?
🦈🧊 Your shark/iceberg: Which dangers or obstacles approach us?
💨 Your tailwind: What drives us forward?
🏝💰 Your paradise: What achievement or milestones are we working towards?
Ideas & formats for sprint retrospectives 5
Health Check Retro: Team morale 😇
Maybe your team rarely has anything to complain about – but have you ever really gone into the details? The Morale Health Check Retrospective gives your team 6 statements and each team member anonymously votes on how much they agree with them. Some interesting insights are guaranteed.
Note: This retrospective format asks for agreement with the given Health Check items on a scale.
Health Check Items (scale)
Appreciation: My colleagues appreciate my contribution to the team.
Team Spirit: There is a trusting working atmosphere in our team.
Transparency: Everyone in my team knows who is currently working on what.
Recovery & Breaks: I have enough room for breaks in which I can draw new energy.
Meeting culture: Our meetings are well structured, yet leave room for creativity and new ideas.
Support: In my team, each team member passes on their individual knowledge and experience.
Ideas & formats for sprint retrospectives 6
Battery retrospective 🔋
You have to charge your cell phone battery every day, but what about your personal battery? Motivation, satisfaction, etc.? In my experience, this metaphor is very popular in teams – the following 4 Sprint Retrospective questions will guide you.
Open feedback questions:
How full is your personal battery as a percentage right now?
What has drained your battery recently?
What has recharged your battery recently?
What would help you to save energy over the next few weeks?
Ideas & formats for sprint retrospectives 7
The Starfish Sprint Retrospective ⭐️
The Starfish Sprint Retrospective uses the visual structure of a starfish to ask five different questions. Experience has shown that one or two fields often remain quite empty, which is why I find this format only mediocre.
 
															Open questions
Keep: [Optional: Looking at the last sprint / weeks] What should we keep doing, keep as it is?
Stop: What should we stop doing?
Start: What should we start doing?
More: What should we do more of?
Less: What should we do less of?
Ideas & formats for sprint retrospectives 8
The Mario Kart Retro 🚗
Mario Kart was not only played by many – in their childhood. This retrospective idea can be particularly suitable for software development teams that include one or two nerds, in order to bring a little more life to the retrospective.
As futurespective
What bananas on the track do we have to look out for?
What’s an upcoming shortcut we could take advantage of?
What powerup could we pick up to ensure our win?
As a retrospective
What shortcuts helped us win?
Which bananas did we slip on?
What was the powerup that gave us an edge?
Ideas & formats for sprint retrospectives 9
News magazine Retro 📰
Many people read or listen to the news every day, which is why everyone understands this retrospective idea: If a journalist were to write about your situation, how would the story be presented? Here, too, I have often experienced how a lively discussion arises.
Retrospective Questions
Let's imagine there was a team magazine: What is the headline of the current issue?
Which controversial topic is currently being discussed?
Which false reports do we need to correct? In other words: Which past assumptions or hypotheses have turned out to be wrong?
What would be the quote of the week?
Bonus tip: Interactive remote retrospective games
Does your team conduct hybrid, remote or virtual retrospectives? Then take a look at this 1-minute video in which I give you a tip on how to increase the retro engagement of your employees guaranteed!
Conclusion - The best sprint retrospective ideas
So, I hope one of the ideas for sprint retrospectives has proven to be convincing. Especially if teams have had little variety in retrospectives so far, these formats should give your retros a positive boost.
If you are interested in even more retrospective templates, then take a look at our corresponding blog post: 54 Retrospective templates for successful agile teams. If this list is too long for you, I have another article that is shorter: My 7 favorite retrospective templates.
FAQ - Questions about Sprint Retrospective ideas
If you had to recommend one sprint retrospective idea, what would it be?
If I really had to choose just one retrospective idea, then I would recommend the battery retrospective. It's an easy format that's easy to understand and can be repeated practically endlessly.
What are typical mistakes when moderating agile sprint retrospectives?
A typical mistake is to believe that your team members are actively reaching out. Some will not yet feel so psychologically secure, others may still have their minds elsewhere. As the moderator, you have the right and the responsibility to regularly go around the circle and ask everyone individually: "What do YOU have to say about this topic?"
If you could only give one tip for retrospectives, what would it be?
Good question – If I could only give one tip for your sprint retrospective, I would say the following: Focus on deriving good measures! If you somehow manage – whether in 10 or 90 minutes – to derive ONE good action that makes your next sprint a little better – then you have officially had an above-average retrospective!
Most Agile Coaches and Scrum Masters run in circles...
...fixing superficial symptoms. Time to use psychology to foster sustainable mindset change.
 
															 
				






