Spells That Worked

What magic helped the team succeed this time?

Our daily standups were sharp and focused, like a well-cast Expelliarmus on wasted time.
Pairing on the tricky payments feature meant we shipped it bug-free.
The new code review checklist worked like a charm and caught issues early.
The Dark Arts

What problems or blockers cast a shadow over us?

Unclear requirements left us wandering in the Forbidden Forest for days.
Too many context switches drained our focus like a Dementor.
The flaky test suite kept us blocked far longer than it should have.
Lessons from Dumbledore

What wisdom or insights did we gain along the way?

We learned that early stakeholder demos save us a lot of rework.
Smaller, more frequent releases reduce our risk dramatically.
Asking for help sooner would have unblocked us days earlier.
Wishes from the Sorting Hat

What magic do we want to conjure for next time?

Let's introduce a 'no-meeting' focus block twice a week.
I wish for clearer definitions of done before we start work.
Can we automate the deployment so it's one wave of the wand?

What is the Magical Hogwarts Retrospective?

The Magical Hogwarts Retrospective takes the setting of the Harry Potter books by J.K. Rowling and uses it to frame a normal team retro. The spells that worked are your wins, the dark arts are your blockers, and the Sorting Hat hands out wishes for the next sprint. People who know the books get an extra layer of fun, and everyone else still has clear prompts to answer. The board has four columns, each matching a standard part of a retrospective. Spells That Worked is what went well. The Dark Arts covers the problems and blockers that held the team back, and it's a good column to run anonymously. Lessons from Dumbledore is for the insights the team would pass on to its past self. Wishes from the Sorting Hat is where the team picks the changes and experiments it wants to try, then turns the top-voted ones into actions with owners. Use it when the team is tired of the usual format, around a milestone or a team social, or when a hard topic needs a lighter way in. It works the same way for remote and co-located teams.

Magical Hogwarts retrospective format

Spells That Worked

What magic helped the team succeed this time?

This is your 'what went well' column. Ask the team to celebrate the practices, decisions and collaborations that produced good results. Naming what worked helps the team repeat it and starts the session on a positive note.

The Dark Arts

What problems or blockers cast a shadow over us?

This is your 'what didn't go well' column. Make it safe for people to name the obstacles and frustrations that held the team back. Consider keeping contributions anonymous so sensitive issues come out without blame.

Lessons from Dumbledore

What wisdom or insights did we gain along the way?

This column is for lessons learned. Ask what the team understands better now and what advice it would give its past self. These insights connect what happened to what you'll do differently next time.

Wishes from the Sorting Hat

What magic do we want to conjure for next time?

This is your actions column. Invite the team to suggest the changes, experiments and commitments it wants to make, then turn the most-voted wishes into actions with owners so they carry into the next sprint.

When to use this retrospective

  • When your team has retro fatigue and needs a fresh, playful format.
  • At milestone or end-of-quarter celebrations where you want to recognize wins in a memorable way.
  • When a new or cross-functional team is forming and you want a low-pressure way to start talking.
  • Around themed events, holidays or team socials where a story-driven retro fits the mood.
  • When difficult issues need raising and a light metaphor makes it easier to be honest.

Suggested icebreaker questions

  • Which Hogwarts house would the Sorting Hat place you in, and why?
  • If you could cast one real-life spell to improve your workday, what would it do?

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 before you start. A quick 'sorting' of the team into houses or a themed background gets people in the mood.
  • Keep the metaphor light and explain each column in plain terms, since not everyone is a fan.
  • Timebox each column to keep energy up and stop the theme from drifting into off-topic chat.
  • Use anonymous input for The Dark Arts so people feel safe raising sensitive issues.
  • Group and vote before you discuss, so the team spends its time on the issues that matter most.
  • Turn Wishes from the Sorting Hat into actions with owners so the ideas lead to change.

Frequently asked questions

How long does a Magical Hogwarts Retrospective take?
Most teams finish in 45 to 60 minutes. Allow a little extra time at the start if you're doing a themed icebreaker or a house sorting.
When should I use a themed retrospective like this one?
Use it when your team has retro fatigue, is celebrating a milestone, or needs a low-pressure way to raise issues.
How is this different from a standard sprint retrospective?
It covers the same ground (wins, problems, lessons and actions) but frames it with Hogwarts imagery, which makes the session easier to remember and often easier to speak up in.
Do all team members need to be Harry Potter fans?
No. Each column has a plain prompt, so people who haven't read the books or seen the films can take part fully. The theme is just a framing device.
Can I run this retrospective with a remote team?
Yes. In TeamRetro everyone adds ideas privately and at the same time, then the team groups, votes and discusses together, which works well for distributed and hybrid teams.
How do I make sure the fun theme still produces real outcomes?
Use grouping and voting to focus the discussion, then turn the top wishes into actions with owners and review them at your next retrospective.
Ready to run this retrospective?Try this retrospective live