Scrum retro prompt bank
60 Sprint Retrospective Questions for Scrum Teams
Sprint retrospective questions should connect directly to the sprint that just ended. Use these prompts to inspect the sprint goal, planning, flow, quality, teamwork, and the action item you will actually finish next.
Sprint goal and outcome questions
- How clear was the sprint goal after planning?
- What changed between the sprint goal and the work we actually did?
- Which completed item mattered most to users?
- Which unfinished item should not roll forward unchanged?
- What did we learn from the sprint review?
- Where did we optimise for output instead of outcome?
- What should we do sooner if the sprint goal starts drifting?
- Which stakeholder expectation was unclear?
- What would make the next sprint goal easier to defend?
- What metric or signal should we check before planning?
Planning and scope questions
- Which story was bigger than we thought?
- What acceptance criteria were missing or vague?
- Where did dependencies appear too late?
- What work should have been split before sprint planning?
- What was pulled into the sprint without enough discussion?
- What should we decline or defer next time?
- How realistic was our capacity planning?
- What interrupted planned work most often?
- Which backlog item needs discovery before commitment?
- What would make planning shorter and sharper?
Delivery flow questions
- Where did work wait the longest?
- Which handoff caused avoidable delay?
- How healthy was our review queue?
- What made testing slower than expected?
- Where did context switching hurt delivery?
- Which build, deploy, or environment issue repeated?
- What helped us release with confidence?
- What should we automate or simplify?
- Which blocker should have been escalated earlier?
- What did we do that improved flow?
Quality and technical questions
- What bug or defect taught us the most?
- Where did technical debt change our choices?
- Which code area feels riskier after this sprint?
- What test would have caught an issue earlier?
- Where did our definition of done hold up?
- Where did our definition of done need more detail?
- What refactor would pay off soonest?
- What operational signal should we watch after release?
- Which shortcut was reasonable and which was not?
- What quality practice should we repeat?
Teamwork and action questions
- Who needed help earlier than they received it?
- Where did pairing or swarming help?
- What information did not reach everyone who needed it?
- Which team norm was useful this sprint?
- Which team norm should change?
- What action item from the last retro actually helped?
- What action item from the last retro did we ignore?
- What is the smallest action we can finish before planning?
- Who owns the next improvement and by when?
- What should we check at the next retro to prove this changed?
Remote sprint questions
- Where did remote collaboration help the sprint?
- Where did remote collaboration hide a blocker?
- What should move from chat into the ticket or decision log?
- Which ceremony needs a tighter agenda?
- How can we make async updates easier to scan?
- What should the facilitator do differently next time?
- What question would expose a hidden risk before sprint planning?
- What would make the next sprint feel more sustainable?
- What is one thing we should celebrate before moving on?
- What commitment are we willing to make as a team?
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 retroFAQ
What are good sprint retrospective questions?
Good sprint retrospective questions ask what helped or hurt the sprint goal, where flow broke down, what quality signals appeared, and what one change the team will try next sprint.
How many sprint retro questions should a Scrum Master ask?
Three to five is enough for most teams: one warm-up, two core inspection questions, one action question, and optionally one team-health prompt.
How are sprint retrospective questions different from general retro questions?
Sprint retro questions reference the sprint goal, backlog, ceremonies, definition of done, and work that just shipped. General retro questions can be broader and less tied to Scrum cadence.
Need a structured format for your sprint retro? The retrospective templates guide covers Start/Stop/Continue, 4Ls, Sailboat, and more with facilitation steps and free boards.