The Frights

What scared us or went terribly wrong this sprint?

A production deploy failed at 5pm on Friday and we all jumped out of our skins.
The requirements changed three times mid-sprint. Truly terrifying.
We discovered a giant pile of technical debt lurking in the legacy module.
The Survivors

What went well and helped us live to tell the tale?

Our pairing sessions slayed a nasty bug in record time.
The new CI pipeline caught problems before they could haunt us.
Great teamwork meant nobody got left in the dark.
Lurking Monsters

What risks or problems are still hiding in the shadows?

The scaling limits on our database feel like a beast waiting to wake up.
Onboarding docs are out of date and could trip up the next new hire.
We're relying on one person who knows the payment system. That's a single point of fright.
Protective Spells

What actions or improvements will keep us safe next sprint?

Add a deploy freeze window so no one ships right before the weekend.
Schedule a tech-debt slaying session every sprint.
Write and rehearse an incident runbook to banish on-call panic.

What is the Friday the 13th Horror Sprint Retrospective

Every sprint has its jump scares, its lurking monsters and a few survivors who lived to tell the tale. The Friday the 13th Horror Sprint Retrospective gives your team review a horror-movie theme. Setbacks become frights and wins become survivors, and that small shift makes uncomfortable issues easier to say out loud. The board has four topics. The Frights is for what scared you or went badly wrong. The Survivors is for what went well and got you through. Lurking Monsters covers risks and problems that haven't struck yet, and Protective Spells is where the team agrees on improvements for next sprint. The theme keeps the mood light, so people are less defensive about the hard topics. Under the costumes it's a full retrospective: you surface hidden risks, recognize the people who held things together and leave with actions that have owners. Run it around Halloween, on an actual Friday the 13th, or any time your team needs a break from the usual format.

Friday the 13th Horror Sprint retrospective format

The Frights

What scared us or went terribly wrong this sprint?

This is where the team names what gave them a fright during the sprint: the bugs, blockers and surprises that made everyone scream. Remind people the spooky framing is there so they can share even the scariest issues. Ask follow-up questions until you reach the root cause of each fright.

The Survivors

What went well and helped us live to tell the tale?

Celebrate the wins, the heroes and whatever helped the team get through the sprint intact. Make room for individual and team wins alike, and name the habits that worked so they get repeated next sprint.

Lurking Monsters

What risks or problems are still hiding in the shadows?

This topic is for threats that haven't struck yet but are getting closer: risks, fragile areas and unresolved issues. Ask people to name things they suspect could become a problem, even if they aren't sure. Spotting them early lets you set a trap 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, give it an owner and keep it achievable within the next sprint. This is the payoff of the retro, so give it enough time.

When to use this retrospective

  • Around Halloween or on an actual Friday the 13th, when you want a seasonal twist on your usual sprint review.
  • When your retrospectives have become routine and the team needs a different format to get people talking.
  • After a chaotic or difficult sprint, when a playful theme helps the team discuss tough issues without getting defensive.
  • When you want to celebrate wins and also flush out hidden risks before they turn into 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?

Want a warm-up your team plays, not just answers out loud? Browse free icebreakers →

Ideas and tips for your retrospective meeting

  • Set the mood with costumes, virtual backgrounds or eerie music.
  • Use the metaphor, but make sure each fright and monster maps to a real problem the team can act on.
  • Timebox each topic so the fun doesn't run away with you and you still reach Protective Spells.
  • Tell the team the horror framing is there to make scary or sensitive issues easier to raise without blame.
  • Give everyone time to add ideas on their own before grouping and discussing, so quieter voices aren't drowned out.
  • Finish by giving each Protective Spell an owner and a due date so the improvement actually happens.

Frequently asked questions

When should I use the Friday the 13th Horror Sprint retrospective?
Use it around Halloween, on an actual Friday the 13th, or whenever your team is tired of the standard format. It also works after a chaotic sprint, when a playful theme makes tough topics easier to discuss.
How long does this retrospective take?
Plan for 45–60 minutes with a team of five to eight people. That leaves time to brainstorm each topic, group ideas, discuss and agree on actions.
How is it different from a standard sprint retrospective?
It covers the same ground (what went well, what went wrong, risks and improvements) under a horror theme. The Frights, The Survivors, Lurking Monsters and Protective Spells make it easier to raise difficult issues.
Will the spooky theme distract from real outcomes?
Not if you tie each metaphor to a concrete problem and timebox the discussion. The Protective Spells topic means you still finish with clear actions that have owners.
Is this format suitable for remote teams?
Yes. In TeamRetro everyone adds ideas privately, votes on what matters most and discusses live, so remote team members take part the same way as people in the room.
Ready to run this retrospective?Try this retrospective live