Treasures Found

What wins or successes did we discover this sprint?

We shipped the new onboarding flow ahead of schedule and got great early feedback.
Our daily standups were tight and focused this sprint, with no rambling.
I finally cracked that caching bug that had been haunting us for weeks.
Traps and Tricks

What obstacles, blockers or sneaky problems slowed us down?

Unclear requirements meant we built the wrong thing twice.
The staging environment kept breaking and ate hours of our time.
Too much context switching between projects killed my focus.
Three Wishes

If the genie granted three wishes, what would we improve?

I wish we had a stable test environment that never went down.
I wish requirements were locked in before the sprint started.
I wish we protected one focus day a week with no meetings.
Magic Carpet Ride

Where do we want to go next and what's our first step?

Let's set up a recurring check on staging health every morning.
We'll trial a no-meeting Wednesday next sprint.
I'll talk to the other team's lead about syncing on dependencies earlier.

What is Aladdin's Agile Adventure retrospective?

Aladdin's Agile Adventure turns your sprint or project review into a story most people already know. Each column borrows part of the tale: the treasure in the Cave of Wonders, the traps along the way, the genie's three wishes and the magic carpet that carries Aladdin on. The theme gets the team out of its usual retro habits and makes it easier to talk honestly. The board has four columns. Treasures Found is for your wins. Traps and Tricks covers the obstacles and blockers that slowed you down. Three Wishes asks what the team would improve if a genie granted it, and Magic Carpet Ride turns those wishes into next steps with owners. The playful framing lowers people's guard and gives quieter team members an easy way in, and it keeps a long-running team from getting bored of the same format. Stories are how most people make sense of what happened, which is why a themed retro like this often brings out things a standard one misses. Whether you run sprints, a kanban flow or project milestones, it gives the retro a fresh setting and still ends with concrete actions.

Aladdin's Agile Adventure retrospective format

Treasures Found

What wins or successes did we discover this sprint?

These are the gold and jewels in the Cave of Wonders: the achievements, breakthroughs and good moments your team found. Celebrate big and small wins, and recognize individual and team contributions. Ask people why something felt like treasure, so the team can repeat it.

Traps and Tricks

What obstacles, blockers or sneaky problems slowed us down?

These are the traps, dead ends and Jafar-style tricks that got in the team's way. Keep it blameless and focused on what made the work harder than it needed to be. Look for traps that keep coming back, since they may need a systemic fix instead of a one-off patch.

Three Wishes

If the genie granted three wishes, what would we improve?

Time to rub the lamp. Ask the team for the improvements or changes it wishes it had. These wishes become the seeds of your action items. Welcome practical wishes and ambitious ones, since the bold wishes often show what the team really needs.

Magic Carpet Ride

Where do we want to go next and what's our first step?

This is the ride ahead: the team's next steps and direction. Help the group turn its wishes and lessons into concrete, owned actions, and agree who will do what before the next sprint takes off.

When to use this retrospective

  • When your standard sprint retro has gone stale and the team needs a new setting to get talking.
  • After a major milestone or release, to look back on it in a way people will remember.
  • When you want quieter team members to open up. A story lowers people's guard.
  • For end-of-quarter or seasonal retros, where a themed format adds a sense of celebration.
  • When you're introducing a newer team to retrospectives and want something approachable.

Suggested icebreaker questions

  • If a genie granted you one work-related wish right now, what would you ask for?
  • Which fictional character would you most want on your team and why?

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

Ideas and tips for your retrospective meeting

  • Open with a line or two of story so everyone knows how each column maps to the Aladdin theme.
  • Keep it light without losing focus. Timebox each column, since the goal is still real actions.
  • Ask for specifics in Treasures Found and Traps and Tricks, so wins can be repeated and obstacles fixed.
  • Dot-vote the Three Wishes so the team puts its energy into the improvements that matter most.
  • Make sure every Magic Carpet Ride action has a clear owner and a due date before you close.
  • Rotate the facilitator each time you run a themed retro, so the sessions don't all feel the same.

Frequently asked questions

How long does an Aladdin's Agile Adventure retrospective take?
Most teams finish in 45–60 minutes. Allow a few minutes at the start to introduce the theme and a few at the end to confirm who owns each action.
When should I use this themed retrospective?
When the team needs a break from the standard format, after a big milestone, or for a seasonal or celebratory retro.
How is it different from a standard sprint retrospective?
It covers the same ground as any retro (wins, problems, improvements and next steps) but tells it as an Aladdin story, which makes people more relaxed about speaking up.
Does the playful theme reduce the quality of outcomes?
No. The story wraps around ordinary retro prompts. With timeboxing and owned actions, you get the same concrete outcomes as any structured retrospective.
How many people can take part?
It suits teams of about 3–10 people. With a larger group, split into smaller carpets and merge what you find at the end.
Ready to run this retrospective?Try this retrospective live