Mission Victories

What battles did we win this mission?

We shipped the new login feature ahead of schedule, a clear win for the squad.
Our defect rate dropped noticeably this sprint, which felt like a real victory.
I'm proud we supported each other when the production incident hit; nobody was left behind.
The Shield (What Protected Us)

What strengths and practices kept us safe?

Our daily standups kept everyone aligned and caught issues early.
Solid test coverage shielded us from a nasty regression.
Pair programming helped us hold the line on quality.
Enemy Forces (Obstacles)

What threats slowed our advance?

Unclear requirements kept ambushing us mid-sprint.
Too much context switching slowed everyone down.
Flaky CI pipelines cost us hours of waiting.
Next Mission (Plan of Attack)

What's our strategy for the next mission?

Let's lock down requirements before pulling stories into the sprint.
We should protect two hours of no-meeting focus time each day.
Assign an owner to investigate and fix the flaky CI tests.

What is the Captain America's Agile Mission retrospective?

Captain America's Agile Mission retrospective treats your last sprint or project as a mission. The theme borrows from the comic-book hero known for leading a team and carrying a shield, and it asks your team to look at what it won, what protected it, what fought against it and what the plan is for next time. The board has four areas. Mission Victories is for wins, big and small. The Shield covers the practices and habits that kept the team safe, such as test coverage or a good incident playbook. Enemy Forces collects the blockers, from unclear requirements to flaky pipelines. Next Mission turns the discussion into a short plan of attack with owners. Casting obstacles as enemies the whole team fights together keeps the conversation blameless, and the theme gives a routine retro some energy. Use it to close a sprint or project, or when a newly formed team needs a sense of shared purpose.

Captain America's Agile Mission retrospective format

Mission Victories

What battles did we win this mission?

Celebrate the wins and breakthroughs from the period you're reviewing. Ask for specific accomplishments, from big milestones to small heroic acts, and prompt quieter team members to share their proudest moment. Naming victories tells the team which behaviors to repeat.

The Shield (What Protected Us)

What strengths and practices kept us safe?

The Shield is the habits and strengths that protected the team and kept things running, such as strong code reviews, good communication or a useful ritual. Name the practices worth keeping so everyone knows what to fall back on under pressure.

Enemy Forces (Obstacles)

What threats slowed our advance?

Enemy Forces are the blockers and friction that worked against the team. Treat them as enemies to fight together, not personal failings, so the conversation stays constructive. Dig into root causes so you can plan how to deal with each one next mission.

Next Mission (Plan of Attack)

What's our strategy for the next mission?

Next Mission turns the discussion into a plan of attack. Ask for specific improvements the team can commit to, keep the list to a few high-impact actions, and give each one an owner.

When to use this retrospective

  • When morale needs a lift and you want a themed way to celebrate wins.
  • At the end of a sprint or project, to review victories, defenses and obstacles.
  • When the team has faced serious blockers and you want to treat them as shared enemies to tackle together.
  • For newly formed or cross-functional teams that need a sense of shared mission.

Suggested icebreaker questions

  • If you could have one of Captain America's qualities (strength, leadership, or that unbreakable shield), which would help your team most right now?
  • What's a superhero team-up (real or fictional) that reminds you of how this squad works together?

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

Ideas and tips for your retrospective meeting

  • Use the mission theme to keep energy up, but tie every discussion back to something the team can act on.
  • Frame obstacles as enemy forces the team fights together, which keeps feedback blameless.
  • Use dot voting to prioritize the victories, threats and next actions that matter most.
  • Give each Next Mission action an owner and a due date so it doesn't get lost after the session.
  • Make room for quieter team members to add their wins and concerns.
  • Timebox each topic so you have enough time left to agree on your plan of attack.

Frequently asked questions

What is the Captain America's Agile Mission retrospective?
It's a themed retrospective that frames your team's reflection as a mission. Its four areas (Mission Victories, The Shield, Enemy Forces and Next Mission) cover wins, strengths, obstacles and the plan for next time.
When should I use this retrospective format?
Use it at the end of a sprint or project, especially when morale is low or your usual format has gone stale.
How long does it take to run?
Plan for 45–60 minutes, depending on team size. That leaves time to gather ideas in all four areas, discuss the main themes and agree on actions for the next mission.
How is it different from a standard sprint retrospective?
It covers the same ground as a standard retrospective, but the mission theme casts obstacles as shared enemies instead of individual failings, which makes problems easier to raise.
Can remote and distributed teams use this format?
Yes. In TeamRetro everyone adds ideas, groups themes and votes together, live or asynchronously, whether the team is remote, hybrid or in one room.
Do team members need to know Marvel or Captain America to take part?
No. The theme is only a framing device. The prompts make sense on their own, so anyone can take part without knowing anything about superheroes.
Ready to run this retrospective?Try this retrospective live