RPG Retrospective

Run your sprint retro as a role-playing game.

Try this retrospective live

For The Win

What were our achievements in the last sprint?

Successfully deployed the new authentication system: achievement unlocked
Cleared our bug backlog: party bonus XP earned
Completed user research ahead of schedule: speed run achievement
Level Up

What attributes should we level up next?

Need to increase our code review speed stat
Should level up our documentation skills to tier 2
Time to upgrade our deployment pipeline equipment
Side Quests

What side quests did we complete?

Mentored a junior developer in React: teaching skill increased
Created helpful documentation while fixing bugs: Wisdom +1
Helped marketing team with technical review: alliance strengthened
Boss Fight

What are the big challenges coming our way?

Major system migration approaching: level 80 boss battle
Technical debt in core module: hidden boss discovered
Tight deadline for Q4 release: time trial boss incoming

What is the RPG Retrospective?

The RPG (role-playing game) Retrospective is a retrospective game built on ideas most gamers already know. Wins are completed quests, improvements are skills to level up, unplanned work earns bonus XP, and the next big challenge is a boss fight. It gives your team a playful way into the usual questions without changing what the retro is for. The board has four areas. For The Win is for the sprint's achievements, big and small. Level Up covers the skills, processes and tools the team wants to improve. Side Quests is for useful work that wasn't part of the plan, like helping another team or tidying up code while fixing a bug, and Boss Fight looks ahead to the big challenges coming your way. It works especially well with software teams and anyone who plays games, but keep the references simple so nobody feels left out. Because Boss Fight looks forward, you finish knowing what's ahead as well as what's behind you, and the Level Up items turn naturally into actions.

RPG retrospective format

For The Win

What were our achievements in the last sprint?

Treat the team's accomplishments as completed quests. Celebrate the big wins and the small ones, the way a game rewards main quests and side missions alike. Gaming terms like 'critical hit' or 'rare item found' keep the theme going.

Level Up

What attributes should we level up next?

Ask the team which skills, processes or tools need improving. Treat it like building a character: each improvement is a skill to train, an attribute to raise or a piece of equipment to upgrade. Pick the one or two that would help most next sprint.

Side Quests

What side quests did we complete?

This area is for useful work that wasn't part of the sprint goal, such as helping another team, learning a new skill or tidying up a process. Side quests often pay off later, so make sure the people who took them on get credit.

Boss Fight

What are the big challenges coming our way?

Present the challenges ahead as boss battles that need strategy and coordination. For each one, ask what equipment (tools), skills and party members (people) the team will need to win.

When to use this retrospective

  • When team morale needs a lift and you want a more playful retrospective
  • With teams that enjoy games or need a fresh way to look at their work
  • When you want the team to think creatively about the challenges ahead
  • For teams that respond well to metaphors and other ways of framing a discussion

Suggested icebreaker questions

  • If your current project was a video game, what genre would it be and why?
  • What's your favorite power-up or special ability in a game, and how could we apply that concept to our team?

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

Ideas and tips for your retrospective meeting

  • Keep the gaming references simple, since not everyone plays games
  • Track action items with health bars or experience points to show progress over time
  • Keep the theme in proportion: it should make the retro easier to run, not distract from it
  • Create a character sheet for the team to track improvements over several sprints
  • Play quiet game music or sound effects to set the atmosphere
  • Rotate the 'Game Master' role so different team members get to facilitate

Frequently asked questions

What is an RPG retrospective?
It's a retrospective game that frames your sprint as a role-playing quest. The team logs achievements in For The Win, picks skills to improve in Level Up, credits unplanned work in Side Quests and plans for the challenges ahead in Boss Fight.
How do you run an RPG retrospective?
Introduce the theme, then give everyone a few minutes to add ideas to each area on their own. Group and vote on them, discuss the top items, and turn the Level Up and Boss Fight items into actions with owners.
When should you use an RPG retrospective?
Use it when morale needs a lift or your usual format has gone stale. It suits software teams and anyone who plays games, and the references are simple enough for everyone else.
How long does an RPG retrospective take?
Plan for 45 to 60 minutes. Allow more if your team wants to spend longer planning for the boss fight.
Do you need to be a gamer to take part?
No. The four areas map to familiar retrospective questions: what went well, what to improve, what else helped and what's coming. Keep the references light for people who don't play games.

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