Zombie Apocalypse Retrospective

Zombie Apocalypse Retrospective format

Survival Wins

What helped us survive and succeed this sprint?

Survival Wins represent the team's successes, effective strategies, and positive outcomes. This topic helps the team recognize what worked well and should be continued. Encourage team members to think about practices, tools, collaborations, or decisions that kept the team 'alive' and thriving during the sprint. Frame these as survival tactics worth repeating.

Zombie Horde

What obstacles and challenges attacked us?

The Zombie Horde represents obstacles, blockers, and challenges that threatened the team's progress. This is where the team identifies what went wrong or what slowed them down. The zombie metaphor makes it easier to discuss problems without blame—zombies are external threats, not personal failures. Encourage specific examples and help the team distinguish between different types of 'zombies' (technical debt, unclear requirements, resource constraints, etc.).

Survival Supplies

What resources or support do we need?

Survival Supplies represent the resources, tools, training, or support the team needs to be more effective. This topic focuses on identifying gaps and what would help the team 'survive' better in future sprints. Encourage the team to think broadly—supplies could be technical tools, knowledge, time, people, or process improvements. Help them be specific about what they need and why it would help.

Fortify the Base

How can we strengthen our defenses and improve?

Fortify the Base is where the team identifies concrete improvements and action items. This represents strengthening processes, practices, and team dynamics to be better prepared for future challenges. Focus on actionable items that address the zombies encountered and leverage the survival wins. Help the team prioritize which fortifications are most critical and ensure each has a clear owner and timeline.

When to use this retrospective

• When your team is experiencing retrospective fatigue and needs a fresh, engaging format to reinvigorate the reflection process and boost participation.
• For teams working through particularly challenging sprints or projects where the apocalypse metaphor helps create psychological safety to discuss difficult issues without blame.
• When you want to build team camaraderie and inject fun into your retrospectives while still achieving meaningful insights and actionable improvements.
• For creative or gaming-oriented teams who respond well to thematic approaches and storytelling as a way to frame their work experiences.
• When introducing retrospectives to a new team and you want to make a memorable first impression that shows reflection can be both productive and enjoyable.

Suggested icebreaker questions

• If the zombie apocalypse started right now, what one item from your desk would you grab as your survival tool?
• Which team member would you want in your zombie apocalypse survival group and why? What's their special skill?

Ideas and tips for your retrospective meeting

• Embrace the theme fully by using apocalypse language throughout the session. Refer to yourself as the 'survivor leader' and encourage team members to stay in character—it increases engagement and psychological safety.
• Watch for blame language disguised as zombie talk. If someone says 'the zombie that is John's code,' redirect to focus on the situation, not individuals. Keep zombies external and systemic.
• Time-box each section to maintain energy and momentum. Apocalypse scenarios are urgent—use a visible timer to create that sense of focused intensity without letting discussions drag.
• Prioritize the 'Fortify the Base' actions ruthlessly. Not every fortification can be built immediately. Help the team identify the 2-3 most critical improvements that will have the biggest impact on survival.
• Use voting or dot-voting to identify which zombies were most threatening and which fortifications are most urgent. This ensures the team focuses on what matters most rather than trying to address everything.
• End on a high note by reviewing the Survival Wins and celebrating the team's resilience. Acknowledge that they've survived another sprint and are stronger for it—this builds momentum for the next iteration.