The questions you ask in a retrospective shape everything that follows. A sharp question opens a real conversation. A generic one produces polite, forgettable answers that lead to no meaningful change.
This guide provides 28 tested retrospective questions organised by purpose, with facilitation tips for each category, questions for specific situations, and guidance on how to pick the right ones for your team's current context.
Why question choice matters
Most retrospective questions are really prompts, and familiar prompts produce familiar answers. Teams that have run dozens of retros often answer "What went well?" on autopilot.
Sharper questions produce sharper responses. Compare:
- "What went well?" → "The sprint planning was good."
- "What's one thing a teammate did this sprint you'd like to see more of?" → "Marta jumped in to unblock the API integration before I even had to ask. That saved us two days."
The second version names a behaviour, credits a person, and gives the team something concrete to reinforce. That's the kind of answer that changes how a team works.
Use the list below as a bank to draw from. Pick 3–5 questions that fit your team's situation rather than cycling through all 28 in a single session.
28 agile retrospective questions
1. For capturing what went well
These questions help the team name specific behaviours and practices worth repeating, not just vague positivity.
- What surprised you this sprint?
- What went really well this sprint?
- What are you grateful for from this sprint?
- What were some of your personal highlights from this sprint?
- What did you learn during this sprint that will help you in the future?
Facilitation tip: Push for specificity. When someone says "communication was better," follow up: "What made it feel different this sprint?" Better answers come from better follow-up, not better silence.
2. For identifying areas for improvement
These questions surface friction without assigning blame. They focus on systems and processes, not individuals.
- What could we have done better this sprint?
- What impediments did we encounter during this sprint?
- What are we doing that is not working well?
- What could we have done differently to achieve our goals?
- What are some of the challenges we faced this sprint?
Facilitation tip: Use anonymous brainstorming mode so team members write candidly before any cards are visible. Honest answers surface more readily when people can't see what others have written. Reveal all cards simultaneously before grouping and discussing.
3. For brainstorming improvements
These questions open the space for new ideas rather than analysing what already happened.
- What are some small changes we could make to improve our process?
- What are some new tools or techniques we could try?
- How can we improve communication and collaboration within the team?
- What can we do to build on our successes from this sprint?
- How can we make our work environment more enjoyable and productive?
Facilitation tip: Defer judgement while ideas are being generated. A quick voting round afterwards is a fairer way to prioritise than debating each idea in real time; it stops the most vocal person in the room from setting the agenda.
4. For prioritising action items
These questions help the team move from insight to commitment.
- Which of these improvements are most important to us?
- What are the most feasible changes we can make?
- What resources do we need to make these changes happen?
- How will we track our progress and measure the impact of our changes?
- What are the potential risks and challenges of implementing these changes?
Facilitation tip: Be ruthless about scope. One well-executed action item beats five forgotten ones. Use TeleRetro's action item tracking to carry commitments forward to the next retro so they don't get lost between sessions.
5. For reflecting on the retrospective itself
These questions improve how you run future retros, not just the next sprint.
- What did we learn from this retrospective?
- What are we committed to doing differently in the next sprint?
- How will we track our progress and make sure we follow through?
- What are some ways to make our retrospectives even more valuable?
6. The four essential questions
If you need to keep a retro short and focused, these four cover the fundamentals:
- What went well?
- What could we have done better?
- What are we going to do differently next time?
- Is there anything else we need to discuss?
They're a reliable baseline: simple, action-oriented, and suitable for teams of any experience level. Don't underestimate question 4: it's where the issues people were reluctant to raise in structured categories often surface.
Questions for specific situations
New team (first 3 sprints)
New teams benefit from questions that build familiarity before tackling process issues head-on.
- "What's one thing you'd like the team to know about how you work best?"
- "What's still unclear about how we make decisions together?"
- "What's one thing that made you feel most included this sprint?"
After a difficult sprint
High-pressure sprints need questions that acknowledge how people are feeling before jumping to solutions.
- "How are you feeling about the sprint, honestly?"
- "What was the hardest moment for you personally?"
- "What do we need to do differently to make the next sprint feel more sustainable?"
Remote or hybrid teams
Distributed teams often have friction points specific to async and remote work.
- "What communication or collaboration challenge was specific to working remotely this sprint?"
- "Was there any moment where you felt disconnected or out of the loop?"
- "What would make remote working easier for you going into next sprint?"
How to use these questions well
Pick questions that fit the sprint, not a formula. A sprint that went badly needs different questions from one that went well. A sprint with a lot of new team members needs different questions from a stable team's 40th retro.
Rotate questions between sprints. Teams that use identical questions sprint after sprint start giving identical answers. Varying at least one category each retro keeps the conversation fresh.
Start with anonymous writing. Give team members time to write answers individually before any are shared. This prevents the first person who speaks from anchoring everyone else's thinking, which is especially important for the "what could be improved" category.
Follow up on vague answers. "Communication was a problem" is not an insight. "We didn't align on the API contract before front-end development started, which caused three rounds of rework" is. The facilitator's job is to surface specifics, not accept generalities.
Frequently asked questions
How many questions should you ask in one retrospective?
Three to five per session is enough. More than that and you're running a survey, not a conversation. Use the bank above to select questions that fit the sprint you've just had.
Should you use the same questions every sprint?
No. Rotating questions keeps the conversation fresh and surfaces different observations. Try varying at least one category each retro, and occasionally try a different format entirely to change the shape of the conversation.
What if team members don't answer honestly?
That's usually a psychological safety issue, not a question issue. If answers are consistently polished and non-committal, try anonymous mode, rotate the facilitator, or use a format like Lean Coffee where the team sets the agenda themselves. Sometimes the best move is a one-on-one conversation before the retro, not a better question during it.
Updated
Experience a better retro
Create a retro in seconds & see for yourself.