Among Us (Agile Edition) Retrospective

Find the impostors quietly slowing down your sprint.

Try this retrospective live

Tasks Completed

What did we accomplish and do well this sprint?

We shipped the new onboarding flow ahead of schedule. Huge crewmate energy.
Daily standups stayed short and focused all sprint.
Pair programming on the payments bug saved us hours.
Suspicious Activity

What felt off, slowed us down or raised red flags?

Tickets kept getting reopened with unclear acceptance criteria.
The staging environment was down for two days and nobody owned it.
We had three meetings that could have been a message.
Spot the Impostor

What is the real root cause secretly sabotaging us?

The impostor is our unclear definition of done causing constant rework.
Too much work in progress means nothing actually finishes.
No clear ownership of shared environments is the real saboteur.
Vote to Eject

What actions will we commit to next sprint?

Eject vague tickets: agree on a definition-of-done checklist by Friday.
Limit WIP to two items per person and enforce it on the board.
Assign a rotating owner for the staging environment each sprint.

What is the Among Us (Agile Edition) retrospective?

The Among Us (Agile Edition) retrospective borrows the social-deduction game, where a crew tries to find the impostors hidden among them. Here the impostors aren't people. They're the hidden blockers, small inefficiencies and unspoken tensions that quietly slow your team down. The theme keeps the stakes low, which tends to get quieter team members talking. The board follows the game. Tasks Completed is for what the team did well, the crewmate work that kept the ship running. Suspicious Activity collects anything that felt off or slowed you down. Spot the Impostor digs past those symptoms to the root cause doing the damage, and Vote to Eject turns the top impostors into actions for next sprint. Because the blame lands on the impostor and never on a person, it's easier to raise uncomfortable issues. It works well when retro fatigue has set in and the team needs a theme most people recognize. Scrum teams, DevOps squads and remote groups can all run it in TeamRetro and come away with a short list of root causes and a plan to deal with them.

Among Us (Agile Edition) retrospective format

Tasks Completed

What did we accomplish and do well this sprint?

This is the crewmate column, where the team celebrates the tasks, wins and good habits that kept the ship running. Recognize delivered work and good behavior alike. Keep the tone upbeat to build momentum before the tougher columns, and ask quieter members for at least one win each.

Suspicious Activity

What felt off, slowed us down or raised red flags?

Here the team reports anything that felt suspicious: friction, delays, confusing processes or a sense that something wasn't right. Calling it suspicious activity instead of blame makes it safer to raise awkward issues. Group similar reports so patterns show up before you move to root causes.

Spot the Impostor

What is the real root cause secretly sabotaging us?

This column looks for the impostors themselves, the root causes behind the suspicious activity. Ask the team to look past symptoms and name the systemic issues, dependencies or process gaps that keep causing trouble. Use the suspicious activity as evidence, and vote on which impostor is doing the most damage.

Vote to Eject

What actions will we commit to next sprint?

This is where the team votes to eject the impostors by deciding what to do about them. Turn the top root causes into concrete, timeboxed actions, each with an owner. Keep the list short and agree how you'll check progress at the next retro, so the changes stick.

When to use this retrospective

  • When your regular sprint retros have gone stale and the team needs a game-style format to get involved again.
  • When you want to find hidden blockers and root causes without anyone feeling blamed.
  • When the team enjoys playful themes and you want quieter members to open up.
  • When you're onboarding a new team and want a light first retro that still produces real action items.

Suggested icebreaker questions

  • If you were the impostor on our team this sprint, what task would you have faked doing?
  • Which fictional crewmate (cautious, chaotic, or always-doing-tasks) best matches your work style this sprint?

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

Ideas and tips for your retrospective meeting

  • Aim the impostor framing at processes and root causes, never at individuals.
  • Timebox each column so the theme doesn't crowd out the actions.
  • Dot-vote on which impostor is doing the most damage before you agree on actions.
  • Enjoy the theme during the icebreaker, then bring everyone back to focus when it's time to commit.
  • Limit how many impostors you eject so the team can deliver the actions next sprint.
  • Start with last retro's actions to check whether the previous impostors were really ejected.

Frequently asked questions

How long does the Among Us (Agile Edition) retrospective take?
Most sessions take 45–60 minutes for a team of five to eight. Allow extra time if you want to make more of the theme and the icebreaker.
When should I use this retrospective?
When your standard sprint retros feel repetitive and you want to get the team interested again while still finding real blockers and root causes. Teams that like game-style formats enjoy it most.
How is it different from a standard sprint retrospective?
It uses the Among Us theme to frame the retro as a hunt for impostors, the hidden root causes of problems. Pointing at an impostor instead of a person makes difficult issues easier to discuss.
Does the impostor framing risk blaming team members?
Not if you set the rule up front: the impostor is always a process, dependency or root cause, never a person. Repeat it if the conversation starts drifting toward individuals.
Is this retrospective suitable for remote teams?
Yes. In TeamRetro, distributed teams add ideas, group them and vote on actions together, live or asynchronously.
How many people can take part?
It suits three to ten people. Larger groups can run it with tighter timeboxes and breakout discussions.

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