2 Fun Pokemon-style Agile Retrospectives
You just searched for the “Pokemon Retrospective” on Google 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:
Open Feedback Questions
Party Pikachu - What made us celebrate this sprint cycle?
Angry Pika-Pika - What made us negative?
Raichu - What shoulod we evolve?
Pokemon Retrospective - Pika-Chu Retro Examples:
As seen in the chart, there are the following 3 questions in our Pikachu Retrospective:
- 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 worked out so well lately! (More info on: “ agile metrics %E2%80%9E)
- 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).
Open Feedback Questions
Type Fire - What sparked our fire this sprint? 🔥
Type Combat - what did we have to fight for, what caused recoil? ✊
Type Plant - What seed should we sow (What should we introduce)? 🍃
Pokemon Retrospective - Pokemon Types Retro Examples:
As seen in the chart, there are the following 3 questions at our Pokemon Types Retrospective:
- Fire Type - What ignited our fire this sprint?:
- Example: This week we were able to significantly reduce the product backlog. That has motivated me a lot.
- Fighting Type - 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.
- Plant Type - What seed should we sow (What should we introduce)?:
- Example: You have the feeling that not everyone in your team dares to speak up. The so-called “psychological safety” should be improved. So you could start doing an agile team health check in 3 steps in the team. (More info on: “ psychological safety %E2%80%9C or “ Team health check in 3 steps %E2%80%9E)
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: 22 Refreshing Agile Retrospective Templates in 2023
