How to Run a Sprint Retrospective in English
Learn the English phrases for facilitating a sprint retrospective that surfaces honest feedback and produces concrete action items.
A retrospective only works if people say what actually happened, not what sounds diplomatic — and the facilitator’s phrasing sets that tone from the first sentence. The goal is a conversation that’s honest but not accusatory, and that ends with specific commitments rather than a vague sense that “we should communicate better.”
Opening the Retrospective
Set an honest, blameless tone before asking anyone to share.
- “Let’s start with the ground rule we always use: we’re looking at what happened, not who’s at fault — assume everyone did their best with the information they had.”
- “I want to hear both what went well and what didn’t — genuinely, not just the polite version of either.”
- “Let’s go around and each share one thing that felt good this sprint, and one thing that felt frustrating.”
Drawing Out Specifics
Push gently past vague statements toward concrete detail.
- “When you say communication was rough, can you point to a specific moment where that showed up?”
- “That’s helpful — can you say more about what exactly made that handoff feel unclear?”
- “I want to make sure I understand the actual impact — did that delay affect the release date, or just this task?”
Naming Patterns Without Blame
Surface recurring issues in a way that focuses on the pattern, not the person.
- “This is the second sprint in a row we’ve had scope creep mid-sprint — I think that’s worth digging into as a pattern, not a one-off.”
- “A few of us mentioned feeling blocked waiting on the same review — let’s talk about whether that’s a process gap rather than anyone being slow.”
- “I noticed a theme across a few comments around unclear requirements going in — does that match what others experienced?”
Converting Discussion Into Action Items
End discussion points with something specific and owned, not a vague intention.
- “So the concrete action here is: [specific person] will draft a template for handoff notes before next sprint.”
- “Let’s turn that into something we can actually check on — who owns following up on this, and by when?”
- “I want to avoid this becoming a ‘we should communicate more’ item with no owner — what’s one specific thing we’ll try differently next sprint?”
Closing the Retrospective
Summarize commitments clearly so nothing gets lost after the meeting ends.
- “So to summarize, we have three action items, each with an owner and a date — I’ll post these in the channel right after this call.”
- “Thanks for being honest today — that’s what actually makes these sessions worth the time.”
- “Let’s check in on these action items briefly at the start of next retro, so they don’t just quietly disappear.”
Vocabulary Reference
| Term | Meaning |
|---|---|
| Retrospective | A recurring meeting to reflect on a past sprint or period of work |
| Blameless | An approach that focuses on systems and processes rather than individual fault |
| Action item | A specific, owned task committed to as a result of a discussion |
| Scope creep | The gradual, often unplanned expansion of a task’s requirements mid-sprint |
| Pattern (recurring issue) | An issue that has shown up across multiple sprints, not just once |
Key Takeaways
- Open with an explicit blameless framing before asking anyone to share, so people feel safe being honest.
- Push gently past vague statements toward specific, concrete examples of what actually happened.
- Name recurring patterns explicitly rather than treating each sprint’s issues as isolated incidents.
- Convert every significant discussion point into a specific, owned action item with a date, not a vague intention.
- Close by summarizing commitments clearly and follow up on them at the start of the next retrospective.