2 Fun Pokemon-style Agile Retrospectives
You just searched Google for “Pokemon Retrospective” and want an online template for it? Then you’ve come to the right place, because I’ve prepared two retrospectives for you. Gonna catch them all? Let’s go!
Pokemon Retrospective #1
The Pika-Chu Retrospektive⚡️⚡️⚡️
Who doesn’t know the little yellow mouse? This Pokemon retrospective is based on the pattern we find in many other retrospectives. Looking at the last Sprint cycle, these 3 questions are asked:
Pika Chu Retrospective: How the retro works
Random Icebreaker (2-5 minutes)
Echometer provides you with a generator for random check-in questions.
Review of open actions (2-5 minutes)
Before starting with new topics, you should talk about what has become of the measures from past retrospectives to check their effectiveness. Echometer automatically lists all open action items from past retros.
Discuss retro topics
Use the following open questions to collect your most important findings. First, everyone does it themselves, covered. Echometer allows you to reveal each column of the retro board individually in order to then present and group the feedback.
- Party Pikachu: What gave us cause to celebrate this sprint cycle?
- Angry Pika-Pika: What put us in a negative mood?
- Raichu: What should we continue to develop?
Catch-all question (Recommended)
So that other topics also have a place:
- What else would you like to talk about in the retro?
Prioritization / Voting (5 minutes)
On the retro board in Echometer, you can easily prioritize the feedback with voting. The voting is of course anonymous.
Define actions (10-20 minutes)
You can create a linked action via the plus symbol on a feedback. Not sure which measure would be the right one? Then open a whiteboard on the topic via the plus symbol instead to brainstorm root causes and possible measures.
Checkout / Closing (5 minutes)
Echometer enables you to collect anonymous feedback from the team on how helpful the retro was. This creates the ROTI score ("Return On Time Invested"), which you can track over time.
Pika Chu Retrospective
Pokemon Retrospective - Pika-Chu Retro Examples:
As shown in the diagram, our Pikachu retrospective includes the following 3 questions:
- Party Pikachu - What made us celebrate this sprint cycle?:
- Example: We were able to make our Daily Scrum more compact and save valuable time. - That worked great!
- Angry Pika-Pika - What put us in a negative mood?:
- Example: It’s good to look at agile metrics like your team’s velocity from time to time – that hasn’t gone so well lately! (More info on: agile metrics)
- Raichu - What should we develop further?:
- Example: We are not getting our product backlog managed well. We should think about solutions for this and look at tools if necessary.
Pokemon Retrospective #2
The Pokemon Types Retrospective 🔥✊🍃
This Pokemon Retrospective is based on the Pokemon types “Fire, Fighting and Plant”. Believe me, each of these types is very effective in its own way (pun intended).
Pokémon Type Retrospective: How the retro works
Random Icebreaker (2-5 minutes)
Echometer provides you with a generator for random check-in questions.
Review of open actions (2-5 minutes)
Before starting with new topics, you should talk about what has become of the measures from past retrospectives to check their effectiveness. Echometer automatically lists all open action items from past retros.
Discuss retro topics
Use the following open questions to collect your most important findings. First, everyone does it themselves, covered. Echometer allows you to reveal each column of the retro board individually in order to then present and group the feedback.
- Fire type: What sparked our fire this sprint? 🔥
- Fighting type: What did we have to fight for, what caused a backlash? ✊
- Grass type: What seed should we sow (what should we introduce)? 🍃
Catch-all question (Recommended)
So that other topics also have a place:
- What else would you like to talk about in the retro?
Prioritization / Voting (5 minutes)
On the retro board in Echometer, you can easily prioritize the feedback with voting. The voting is of course anonymous.
Define actions (10-20 minutes)
You can create a linked action via the plus symbol on a feedback. Not sure which measure would be the right one? Then open a whiteboard on the topic via the plus symbol instead to brainstorm root causes and possible measures.
Checkout / Closing (5 minutes)
Echometer enables you to collect anonymous feedback from the team on how helpful the retro was. This creates the ROTI score ("Return On Time Invested"), which you can track over time.
Pokémon Type Retrospective
Pokemon Retrospective - Pokemon Types Retro Examples:
As seen in the chart, there are the following 3 questions at our Pokemon Types Retrospective:
- Type Fire - What ignited our fire this sprint?:
- Example: This week we were able to significantly reduce the product backlog. That has motivated me a lot.
- Type Fighting - What did we have to fight for, what caused recoil?:
- Example: Deadlines that are too tight make every day a struggle. This will set us back in the long run.
- Type Plant - What seed should we sow (What should we introduce)?:
- Example: You feel that not everyone on your team dares to speak up. So-called “psychological safety” should therefore be improved. One way to start would be to carry out an agile team health check in 3 steps within the team. (More info on: psychological safety or Team health check in 3 steps)
Conclusion - Pokemon Retrospectives⚡️🔥✊🍃
Are you and your team real Pokemon trainers? Then I hope you’ll enjoy these two Pokemon retrospectives and that they bring a smile to your team’s faces.
If you want to see more extraordinary retrospectives, you might like this article: 26 Refreshing Agile Retrospective Templates in 2026
