Top Guns

What were our standout wins this mission?

We shipped the new login flow ahead of schedule with zero hotfixes afterward.
Maria absolutely nailed the client demo. Total ace move.
Our automated tests caught three bugs before they ever reached production.
Turbulence

Where did we hit friction or run into trouble?

Unclear requirements meant we reworked the dashboard twice.
The staging environment was down for half the sprint and stalled testing.
Too many context switches between projects broke our flow.
Wingman Support

How well did we back each other up as a team?

Pairing on the tricky API integration saved us a ton of time.
Thanks to whoever jumped in to cover my tickets while I was out.
Our daily standups kept everyone aligned and aware of blockers.
Next Mission

What actions will set us up for the next flight?

Lock requirements before kickoff with a quick clarity check.
Set up monitoring so we catch environment outages sooner.
Introduce a review SLA to prevent end-of-sprint bottlenecks.

What is the Top Gun Squadron retrospective?

The Top Gun Squadron retrospective runs your sprint review like a squadron debrief after a mission. Pilots go over what happened while it's fresh, credit the people who flew well and agree on what changes before the next flight. Your team does the same. The board has four stations. Top Guns is for standout wins and the people behind them. Turbulence covers the friction and problems that slowed the team down. Wingman Support looks at how well people backed each other up, and Next Mission turns everything into actions, each with a pilot who owns it. The aviation theme gives the meeting some energy without getting in the way of the substance. Turbulence is easier to talk about when it's framed as part of every mission, and the Wingman station gives a sprint's quieter teamwork the attention it usually misses. Use it when your retros have gone stale, or after a release that had both big wins and rough patches.

Top Gun Squadron retrospective format

Top Guns

What were our standout wins this mission?

Start by celebrating the wins and the people who made them happen. Ask for specific victories, like a smooth deployment or a clever fix, and prompt quieter members to nominate teammates so credit is shared across the squadron.

Turbulence

Where did we hit friction or run into trouble?

Surface the challenges, blockers and bumpy moments without pointing fingers. Every mission hits some turbulence, and the point is to understand it, not to blame the pilot. What you find here feeds the Next Mission station.

Wingman Support

How well did we back each other up as a team?

This station looks at collaboration: the moments people stepped in to help, and the moments someone wished they had. Ask where support flowed well and where the team was flying without cover.

Next Mission

What actions will set us up for the next flight?

Turn the debrief into a flight plan. Capture specific, achievable actions, assign a pilot to each, and tie them back to the wins and turbulence you discussed so the team can see why each one matters.

When to use this retrospective

  • When your retrospectives feel stale and you want a themed format to get people talking.
  • After a high-stakes release or sprint, when the wins and the problems both deserve time.
  • When you want to look at how well the team backs each other up, not only at what it delivered.
  • For teams that open up more when a metaphor puts some distance between them and the problem.

Suggested icebreaker questions

  • If you had a fighter pilot callsign, what would it be and why?
  • What's one mission (project or task) you felt like an ace flying through recently?

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 quick callsign round so everyone gets into the theme.
  • Keep the metaphor light and the takeaways concrete. The theme is there to support honest reflection.
  • Use anonymous contributions so Turbulence surfaces real issues without anyone feeling singled out.
  • Timebox each station so the debrief keeps moving.
  • Give every Next Mission action a pilot (owner) and a due date so nothing stalls on the runway.
  • Rotate the facilitator between sessions so the squadron shares ownership of the debrief.

Frequently asked questions

What is a Top Gun Squadron retrospective?
It's a themed retrospective that runs your sprint review as a fighter squadron debrief. The team celebrates wins (Top Guns), examines challenges (Turbulence), looks at teamwork (Wingman Support) and plans ahead (Next Mission).
When should I use this retrospective format?
Use it when your usual retrospectives feel repetitive, after a major release, or when you want to give teamwork more attention while still leaving with improvement actions.
How long does a Top Gun Squadron retrospective take?
A typical session runs 45–60 minutes for a team of five to eight. That covers an icebreaker, brainstorming across the four stations, grouping and voting, and agreeing on actions.
How is it different from a standard sprint retrospective?
It covers the same ground as most retros (wins, challenges and actions) and adds a station for teamwork. The aviation theme makes it easier to raise problems without anyone feeling shot down.
Can remote and distributed teams run this retrospective?
Yes. In TeamRetro everyone adds ideas online, live or asynchronously, then the team groups, votes and assigns actions together, so remote and hybrid squadrons run it the same way as a team in one room.
Ready to run this retrospective?Try this retrospective live