Icebreaker questions for retros
These are tied to the sprint that just finished, not generic team-bonding prompts. Use one of these in the first five minutes of a retro to get every voice into the room before the start/stop/continue conversation begins.
When to use these
Use one as the opening question of a sprint retro. The point is to get every team member to say something specific about the sprint before the retro itself starts; that way the people who would normally stay quiet have already broken the silence by the time the start/stop/continue board comes out. Then run the actual retro in TeamRetro.
The questions
- What's one moment from this sprint that stood out for you?
- What's a small win this sprint that didn't make the demo?
- What's something this sprint made you appreciate about a teammate?
- What's a habit the team picked up this sprint that's worth keeping?
- What's a sprint goal we hit that you're proud of?
- What's a sprint goal we missed that's worth talking about?
- What's a process change from last retro that worked?
- What's a process change from last retro that didn't?
- What's a meeting from this sprint you'd run again unchanged?
- What's a recurring meeting we should reconsider?
- What's a piece of feedback from a stakeholder this sprint that landed?
- What's a decision the team made this sprint that you'd want to remember?
- What's a piece of work this sprint that was harder than it looked?
- What's a piece of work that was easier than expected?
- What's a tool, process, or doc that helped you this sprint?
- What's a tool, process, or doc that got in your way?
- What's a moment of unblocking from this sprint — yours or someone else's?
- What's a tradeoff we made this sprint that you'd revisit?
- What's a working relationship that strengthened this sprint?
- What's a kind of work we're spending too much time on right now?
- What's a kind of work we're under-investing in?
- What's a one-word check-in for how this sprint felt?
- What's a sprint pattern from the last three sprints worth naming?
- What's a piece of context the team should carry into the next sprint?
- What's a small experiment you'd want to try next sprint?
Questions we'd skip
Skip "what's one good thing about this sprint" — too vague, gets generic answers. Skip "share your weather emoji" or "what's your spirit animal for this sprint" — they read as forced fun and the team that's already skeptical of retro warmups will use them as evidence the format is wasted time. Skip questions that effectively pre-stage the start/stop/continue ("what should we stop doing?") — that's the retro itself, and asking it as a warmup means the team has answered before the structured conversation begins.
Games that pair well with these
Common questions
- How is this different from the retro itself?
- The retro produces actions; this just gets every voice into the room. A warmup question is one round of single answers, no follow-up. The retro is the structured conversation that comes after.
- Should the scrum master pick the question?
- Yes. Picking a question that fits the sprint is part of the SM's job; rotating it pre-empts the team tuning it out. Same question every retro stops working in three sprints.
- What about a retro after a particularly bad sprint?
- Pick a question that names the difficulty rather than working around it. "What's a moment of unblocking from this sprint" or "what's a piece of work that was harder than it looked" gives the team permission to say so, which makes the retro itself more honest.
Meetings these questions suit
Run these in the browser with Icebreaker Questions
Share the room link, the wheel picks a question, every teammate answers in turn.
Try Icebreaker Questions