Retro Harbour Create a board

Retrospective question bank

60 Retrospective Questions for Better Team Conversations

Use these questions for retrospective meetings when the team needs more than the same three prompts. Pick a section that matches the mood, add the prompts to a Retro Harbour board, and turn the discussion into visible action items.

Create a Board Browse templates

Start, Stop, Continue questions

  1. What should we start doing next sprint to make work easier?
  2. What small practice would help us learn faster?
  3. What should we start measuring because it affects delivery?
  4. What conversation have we avoided that would help the team?
  5. What should we start documenting before it disappears from memory?
  6. What support do we need from outside the team?
  7. What should we stop doing because it creates noise?
  8. Which meeting, report, or handoff is not worth its cost?
  9. What habit is slowing reviews, testing, or releases?
  10. What should we stop assuming about users or stakeholders?
  11. What keeps appearing in retros without changing?
  12. Where are we over-engineering instead of solving the immediate problem?
  13. What should we continue because it genuinely helps?
  14. Which recent choice protected quality or focus?
  15. What team behaviour should we make more visible?

Mad, Sad, Glad questions

  1. What made you mad because it felt avoidable?
  2. Where did friction waste the most energy?
  3. What decision surprised you in a bad way?
  4. What made you sad about the sprint or team dynamic?
  5. Where did someone get stuck for too long?
  6. What customer or stakeholder signal felt disappointing?
  7. What made you glad to be on this team?
  8. Who helped unblock work in a way worth recognising?
  9. What result felt better than expected?
  10. What moment showed healthy teamwork?

4Ls retrospective questions

  1. What did you like about how we worked?
  2. What did you like about the outcome we shipped?
  3. What did you learn that should change our next plan?
  4. What did we learn about our users, codebase, or process?
  5. What did we lack that made progress harder?
  6. What context, skill, or tooling was missing?
  7. What did you long for during the sprint?
  8. What would make the next retro more useful?
  9. Which lesson should become a team habit?
  10. Which lack should become an action item?

Sailboat retrospective questions

  1. What wind pushed us forward?
  2. Which strengths helped the team move quickly?
  3. What anchor slowed us down?
  4. Which risk is still below the surface?
  5. What rocks should we navigate around next sprint?
  6. What destination are we not aligned on yet?
  7. What cargo are we carrying that no longer matters?
  8. What would give the team a clearer route?

Remote and hybrid team questions

  1. Where did asynchronous communication work well?
  2. Where did remote work hide a problem for too long?
  3. What should be written down before the next sprint starts?
  4. Which discussion should have been async instead of a meeting?
  5. Which meeting should have been live instead of async?
  6. How easy was it for quiet voices to contribute?
  7. What timezone or handoff issue should we fix?
  8. What made collaboration feel human this sprint?
  9. What should we do differently for remote onboarding or pairing?
  10. Which decision needs a clearer owner next time?
  11. What would make the next retro safer and sharper?
  12. What is one action we can finish before the next retro?
  13. What should we revisit in two weeks to see if it improved?
  14. What signal would tell us the next sprint is healthier?
  15. Where can we make the next handoff clearer?
  16. What is one promise we should not make again?
  17. What small win should we repeat deliberately?

Turn these questions into a live board

Paste the prompts into a Retro Harbour board, invite the team with a link, vote, group themes, and export the action items.

Start a free retro
Fun retrospective questions Sprint retrospective questions Retrospective templates Sprint retrospective examples

FAQ

What are good questions for a retrospective?

Good retrospective questions help the team inspect how work happened, not just whether work finished. Use a mix of warm-up, process, collaboration, quality, and action prompts.

How many retrospective questions should I ask?

For a 60-minute retro, choose three to five questions. Too many prompts create a long list of cards without enough time to discuss actions.

Should retrospective questions change every time?

Rotate at least one or two questions every retro. Repeating the same format forever makes people answer from habit rather than reflection.

Looking for a complete format with facilitation steps? Browse the retrospective templates guide — Start/Stop/Continue, 4Ls, Sailboat, Glad/Sad/Mad, DAKI, and timeline retrospectives with example prompts and free boards.