45 of the Best Retrospective Questions (by Goal)

The quality of a retrospective is decided by the quality of its questions. Ask "how did the sprint go?" and you'll get shrugs. Ask a sharp, specific question and you'll get the honest observation that's been sitting unspoken for weeks. Below is a working library of retrospective questions, grouped by what you're trying to surface.

Warm-up questions

Open with something low-stakes to get everyone talking before the harder topics.

• In one word, how did this sprint feel?
• What's one thing you're proud of from the last two weeks?
• If this sprint were a weather forecast, what would it be?

Questions that surface what went well

Reinforcing what works is as important as fixing what doesn't. It tells the team what to protect.

• What went better this sprint than last?
• Which of our habits actually helped us ship?
• When did you feel most effective? What made that possible?
• Who helped you this sprint, and how?

Questions that surface problems

Vague complaints go nowhere. The best problem questions force specificity — the same principle behind Sörk's Outcome Lock, where every piece of feedback names what would be different if it were fixed.

• Where did we lose the most time, and why?
• What slowed you down that shouldn't have?
• What did we avoid talking about this sprint?
• If you could change one thing about how we work, what would have the biggest impact?
• What almost went wrong that we got lucky on?

Questions that dig for root causes

Once a problem is on the table, don't stop at the symptom. These questions push toward the underlying cause.

• What would need to be true for this problem to disappear?
• Is this a one-off, or have we seen it before?
• What's the smallest change that would meaningfully reduce this?
• Who or what is the constraint here — a process, a tool, or a decision?

Questions about collaboration and safety

Team health lives beneath the process. These questions test whether people feel safe enough to be honest — the foundation of every useful retro. (More on that in psychological safety in software teams.)

• Did you feel able to say what you actually thought this sprint?
• Was there a moment you held something back? What stopped you?
• Do you feel your work was noticed and valued?
• Where did communication break down?

Forward-looking questions

Close the loop by pointing the team at the next sprint.

• What's the one improvement worth committing to next sprint?
• What will we check next time to know if it worked?
• What experiment should we try?

Don't ask ten questions. Ask three good ones and give people room to answer honestly.

How to use these questions

Rotate your questions each sprint so the retro doesn't go stale, and match them to a format. If you want a ready structure, pair these with Start, Stop, Continue or the 4Ls. For questions aimed at individuals rather than the whole team, see our one-on-one meeting questions. And for a broader pulse check on team health, try a team health check.