Harry Potter Themed Retrospective

Review your sprint with spells, potions and a Patronus

Try this retrospective live

Lumos

What spells worked? What lit up our path?

Our daily standups felt like a well-cast Lumos: short, sharp, and kept everyone on the same page.
The pair programming sessions were magical. We solved bugs in half the time we expected.
We finally nailed our deployment process. It felt like we'd mastered a new spell after weeks of practice.
Nox

What dark forces blocked or hindered us?

Unclear requirements kept changing mid-sprint. It felt like we were fighting a moving target, like a Boggart that kept shifting shape.
Too many interruptions from outside the team. It was like constant Dementors draining our energy and focus.
We underestimated the complexity of the integration work. The dark forest was darker than we thought.
Polyjuice Potion

What could we transform or improve next time?

We should transform our backlog grooming sessions. They're too long and unfocused. Let's try a new format.
I'd like us to adopt a stronger definition of done. A little Polyjuice Potion to change how we approach quality.
We need to improve how we handle urgent requests mid-sprint. A clearer process would help the whole team.
Expecto Patronum

What new spells should we try to protect and guide us?

Let's try a 'no meeting Wednesday' to give the team deep focus time, our very own Patronus against interruptions.
I'd love to experiment with mob programming for our most complex stories next sprint.
We should try a team working agreement session to align on how we collaborate and communicate.

What is the Harry Potter Retrospective?

The Harry Potter Retrospective brings the wizarding world from J.K. Rowling's books into your team's review of a sprint or project. Each topic is named after a spell or potion from the series, which gives people a shared, slightly playful language for talking about what worked and what didn't. Whether your team is full of Gryffindors charging ahead or Ravenclaws analyzing every detail, there's room for both on the board. The board has four topics. Lumos is for what went well and lit the way. Nox is for the dark forces that blocked you. Polyjuice Potion asks what you'd transform or improve, and Expecto Patronum is for new ideas and actions to protect the team next time. Under the theme these are the familiar retrospective questions, so you still finish with clear actions. Calling a blocker a "dark force" makes it a little easier to raise, and the story gives quieter team members a way in. Use it when your team has retrospective fatigue, when you're welcoming new members, or when the team simply shares a love of the books.

Harry Potter retrospective format

Lumos

What spells worked? What lit up our path?

This is the "what went well?" topic. Lumos is the spell that lights a wand in Harry Potter, so here it stands for the moments, practices and habits that lit the way and made the sprint or project shine. Celebrate these wins before you move on to the challenges.

Nox

What dark forces blocked or hindered us?

Nox is the counter-spell to Lumos that puts the light out. This is the "what didn't go well?" topic, covering the obstacles, blockers and frustrations the team faced. Remind everyone that naming a dark force is about seeing what needs to change, not about blame.

Polyjuice Potion

What could we transform or improve next time?

Polyjuice Potion lets characters transform into someone else, so this topic is about what the team would change, adapt or do differently. Ask for specific changes, not vague wishes.

Expecto Patronum

What new spells should we try to protect and guide us?

Expecto Patronum is the protective charm in Harry Potter, cast by focusing on a happy memory. Here it stands for the new ideas, experiments and actions the team wants to try next. Ask for bold, hopeful ideas: what would protect the team from the next round of dark forces?

When to use this retrospective

  • When your team has retrospective fatigue and needs a themed format to restart the conversation.
  • When onboarding new team members and you want a low-pressure retrospective that gets everyone contributing.
  • When celebrating a major milestone or release and you want to look back in a memorable way.
  • When your team shares a love of Harry Potter and you want to use that common ground.
  • When metaphor and storytelling would make it easier for people to raise difficult topics.

Suggested icebreaker questions

  • Which Hogwarts House (Gryffindor, Hufflepuff, Ravenclaw, or Slytherin) do you think your team belongs to, and why?
  • If you could use one spell from the Harry Potter universe to improve how your team works, what would it be and 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 in the meeting invite with a Harry Potter-themed image so people arrive in the spirit.
  • Invite people to use the theme when writing ideas, and make it clear plain language is just as welcome. The goal is reflection, not a creative writing contest.
  • Don't let the theme take over. The magic is there to help honest conversation, so keep pulling the discussion back to actions.
  • Use Expecto Patronum to close on a forward-looking note, and make sure every action has an owner and a due date before you finish.
  • Not everyone has read the books. Explain each topic's metaphor at the start so nobody feels left out.
  • If the team gets stuck, ask questions like "What would Dumbledore advise here?" or "What would your Hogwarts House do differently?"

Frequently asked questions

What is a Harry Potter retrospective?
It's a themed retrospective that renames the standard questions after spells and potions from Harry Potter: Lumos for what went well, Nox for blockers, Polyjuice Potion for improvements and Expecto Patronum for new ideas and actions.
How do I run a Harry Potter retrospective with my team?
Set the scene with a themed invite and explain each topic's metaphor at the start. Give everyone time to add ideas privately, group and vote, then close with Expecto Patronum to agree on actions with owners.
Is this retrospective template only for Harry Potter fans?
No. A quick explanation of each topic is all anyone needs, and people can write in plain language, so nobody has to know the books or films.
How long does a Harry Potter retrospective take?
Plan for 45–60 minutes. Allow a few extra minutes at the start to explain the theme if some people haven't read the books.
When should you use a themed retrospective like this one?
Use it when your regular format has gone stale, after a milestone, or when you're welcoming new people. Save it for the occasional session so the novelty doesn't wear off.

Related templates

WWE Smackdown Showdown Retrospective

Tag-team your sprint review with a wrestling theme.

Working, Not Working Retrospective

Sort what's working from what isn't, then fix it.

Quarterly Retrospective

Step back from the sprints and review the whole quarter.

Baby Steps Retrospective

Pick one small change your team will actually finish.

Ready to run this retrospective?Try this retrospective live