What is the Friday the 13th Horror Sprint Retrospective
Every sprint has its share of jump scares, lurking monsters and survivors who lived to tell the tale. The Friday the 13th Horror Sprint Retrospective brings a playful horror theme to your team reflection, turning the usual review into a thrilling adventure where the team hunts down the things that went bump in the night. By framing setbacks as "frights" and successes as "survivors," teams can talk about even the most uncomfortable issues in a fun, low-pressure way. The format works by guiding your team through a spooky narrative: what scared us, what monsters are still lurking, who survived the chaos and what spells (improvements) we can cast to protect ourselves next time. Each topic invites honest, candid input while the lighthearted theme reduces defensiveness and encourages participation. It's a great way to keep engagement high during seasonal events, end-of-quarter reviews or simply to shake up a retrospective routine that has grown stale. Beyond the costumes and creepy metaphors, this retrospective delivers real value: it surfaces hidden risks, celebrates resilience and produces clear, actionable improvements. Whether you run it around Halloween, on an actual Friday the 13th, or any time your team needs a morale boost, this themed retrospective helps you confront problems head-on while having a few laughs along the way.
Friday the 13th Horror Sprint retrospective format
The Frights
What scared us or went terribly wrong this sprint?
This is where the team names the things that gave them a fright during the sprint — the bugs, blockers and surprises that made everyone scream. Encourage candour by reminding the team that the spooky framing makes it safe to share even the scariest issues. Ask follow-up questions to understand the root cause of each fright rather than just the symptom.
The Survivors
What went well and helped us live to tell the tale?
Celebrate the wins, the heroes and the things that helped the team survive the sprint intact. Make space for everyone to recognise both individual and team-level victories. Reinforce these survivors so the behaviours that worked get repeated next sprint.
Lurking Monsters
What risks or problems are still hiding in the shadows?
This topic surfaces the threats that haven't fully struck yet but are creeping closer — risks, fragile areas and unresolved issues. Encourage the team to name things they suspect could become a problem, even if they aren't certain. Capturing these early lets you set traps before the monster pounces.
Protective Spells
What actions or improvements will keep us safe next sprint?
Turn the frights and lurking monsters into concrete actions — the spells and wards that will protect the team next time. Make each action specific, assign an owner and keep it achievable within the next sprint. This is the payoff of the retro, so give it enough time and energy.
When to use this retrospective
- Around Halloween or on an actual Friday the 13th when you want a seasonal, morale-boosting twist on your usual sprint review.
- When your retrospectives have become routine and the team needs a fresh, engaging format to spark participation.
- After a particularly chaotic or difficult sprint, where a playful theme helps the team discuss tough issues without defensiveness.
- To balance celebrating wins with proactively surfacing hidden risks before they become real problems.
Suggested icebreaker questions
- If this sprint were a horror movie, what would its title be and who would be the first to go?
- What's the scariest bug, outage or surprise you've ever survived at work?
Ideas and tips for your retrospective meeting
- Set the mood with a spooky theme — encourage costumes, virtual backgrounds or eerie music to get everyone in the spirit.
- Lean into the metaphor but keep the conversation grounded; make sure each fright and monster maps to a real, actionable insight.
- Timebox each topic so the fun doesn't run away with you and you still reach the Protective Spells action items.
- Reassure the team that the horror framing makes it safe to raise scary or sensitive issues without blame.
- Give everyone time to add ideas independently before grouping and discussing, so quieter voices aren't drowned out.
- End by assigning clear owners and due dates to your Protective Spells so the improvements actually happen.
Frequently asked questions
When should I use the Friday the 13th Horror Sprint retrospective?
How long does this retrospective take?
How is it different from a standard sprint retrospective?
Will the spooky theme distract from real outcomes?
Is this format suitable for remote teams?
New to retrospectives? Read our guide on how to run a retrospective →