Bonfires Lit

What wins and milestones did we reach this sprint?

We finally shipped the payment integration that's been haunting us for two sprints. Massive relief.
Pair programming sessions felt like co-op mode, and we cleared blockers way faster together.
Our test coverage crossed 80%, a checkpoint we can actually rest at now.
Bosses We Fought

What major challenges or obstacles tested the team?

The flaky CI pipeline was a relentless boss that kept knocking us back to the start.
Shifting requirements mid-sprint felt like a second phase we weren't prepared for.
Legacy code in the auth module hit hard and had way too much health.
You Died: Lessons Learned

Where did we fail, and what did those deaths teach us?

We underestimated the migration effort. Note to self: always scout the area first.
Skipping the code review shortcut cost us a respawn when the bug came back.
We charged into the deployment without a rollback plan. Lesson learned.
Souls & Upgrades

What improvements and actions will we carry into the next run?

Let's invest souls in stabilizing the CI pipeline before it ambushes us again.
Upgrade our definition of done to include a rollback plan for every deploy.
Cap WIP at three items so we stop overextending mid-fight.

What is the Dark Souls Bonfire Retrospective?

The Dark Souls Bonfire Retrospective borrows the checkpoints from FromSoftware's Dark Souls games. In the game, a bonfire is where you rest, refill your flask and plan your next attempt at a boss that has already beaten you several times. This retrospective gives your team the same pause at the end of a sprint. The board has four columns. Bonfires Lit is for wins and milestones. Bosses We Fought covers the big obstacles that tested the team. You Died: Lessons Learned is where you talk about what went wrong and what it taught you. Souls & Upgrades turns all of that into actions for the next sprint. The theme earns its place in the You Died column. Dark Souls players expect to die over and over, and treating failure as part of the run makes it easier for people to own their mistakes without getting defensive. It suits teams that know the games, but each metaphor takes a sentence to explain to anyone who doesn't.

Dark Souls Bonfire retrospective format

Bonfires Lit

What wins and milestones did we reach this sprint?

Bonfires are the checkpoints the team reached: finished work, breakthroughs and moments of relief. Ask everyone to name at least one, however small. It reminds the team what's working before you get to the hard parts.

Bosses We Fought

What major challenges or obstacles tested the team?

Bosses are the big obstacles that took real effort. Treat them as hard problems, not as someone's fault. Ask what made each one tough and how the team took it on, so you can later vote on which bosses still need a plan.

You Died: Lessons Learned

Where did we fail, and what did those deaths teach us?

In Dark Souls you die a lot, and every death teaches you something about the fight. Keep this column blame-free. For each item, ask what the death taught the team, so the discussion stays on what to do differently next time.

Souls & Upgrades

What improvements and actions will we carry into the next run?

Souls are what you spend to level up. Turn the lessons from the earlier columns into specific actions, each with an owner, and add them in TeamRetro so they're tracked into the next sprint.

When to use this retrospective

  • Your team knows its way around games and you want a themed retrospective with a story to it.
  • Morale has dropped after a sprint full of setbacks, and you want to talk about failures without the mood getting heavy.
  • Your usual Start Stop Continue retros have gone flat and the team needs a change of format.
  • The team hit one or more major obstacles ('bosses') and needs to work out a plan for them.
  • You want the team to get comfortable treating failure as something to learn from.

Suggested icebreaker questions

  • If your past sprint were a Dark Souls boss, what would its name and signature attack be?
  • What's the one 'bonfire' moment recently that made you breathe a sigh of relief?

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

Ideas and tips for your retrospective meeting

  • Set the scene with a bonfire image or quiet Dark Souls music in the background before you start.
  • Keep the You Died column blame-free. Remind everyone you're there to learn from what happened, not to find who caused it.
  • Timebox each column so the boss discussion doesn't take over. Aim for 8–10 minutes per column.
  • Use grouping and voting in TeamRetro to find the boss most worth tackling first.
  • Turn every item in Souls & Upgrades into an action with an owner, so the upgrades actually get equipped.
  • Ask quieter teammates for their input directly. Even a small bonfire counts.

Frequently asked questions

What is a Dark Souls Bonfire Retrospective?
It's a themed retrospective built on Dark Souls metaphors: bonfires for wins, bosses for challenges, deaths for lessons and souls for the improvements you take into the next sprint.
How long does a Bonfire Retrospective take?
Most sessions take 45 to 60 minutes, with 8–10 minutes per column plus time for grouping, voting and assigning actions.
Do team members need to play Dark Souls to take part?
No. Each metaphor takes a sentence to explain, so people who've never played the game can join in fully.
When should I use this retrospective instead of a standard one?
Use it after a sprint with real setbacks, when morale needs a lift, or when your usual format has gone stale.
How is it different from a Start, Stop, Continue retrospective?
Both end in actions. The Bonfire format gives failures their own blame-free column, You Died, which makes it easier to talk honestly about what went wrong.
Can I run a Bonfire Retrospective remotely?
Yes. In TeamRetro everyone can add ideas, group them, vote on the toughest bosses and track the upgrades together, wherever they're working from.
Ready to run this retrospective?Try this retrospective live