Agile Retrospective Phrases: What to Say as a Facilitator
Professional English phrases for Scrum Masters facilitating retrospectives: opening lines, energisers, format transitions, conflict resolution, and closing commitments.
The sprint retrospective is the Scrum ceremony where the team reflects on how they work together and identifies improvements. As a Scrum Master, your job is to facilitate — not dominate — the conversation. That means asking the right questions, holding safe space for honesty, keeping the energy up, and moving toward actionable outcomes. This guide gives you the specific English phrases to do exactly that.
Opening the Retrospective
Your opening sets the tone. Start by creating psychological safety — the confidence that it is safe to speak honestly.
Prime directive reading
Many experienced Scrum Masters open with the Prime Directive, attributed to Norman Kerth:
“Before we begin, let’s take a moment to reflect on the Prime Directive: ‘Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand.’ Let’s hold that spirit as we reflect today.”
Opening energy check
“Welcome everyone. Before we dive in — quick energy check. On a scale from one to five, how are you feeling right now? We’ll go around the room.”
“Let’s start with a quick check-in. One word to describe how this sprint felt. Anything goes — there’s no wrong answer.”
Setting the agenda
“Here’s our agenda for today’s retro: we’ll spend about 10 minutes on what went well, 15 minutes on what we’d like to improve, and 15 minutes on action items. We have enough time to go deep if the conversation calls for it.”
“I’d like us to focus today on one specific area — team communication during the sprint. I noticed some patterns I’d like us to explore together. Does that feel like the right focus?”
Running the Retrospective Format
Start / Stop / Continue
The most common retrospective format. Guide it with:
“Let’s start with ‘What worked well.’ Take three minutes to write sticky notes — anything the team should continue doing. Quantity over quality at this stage.”
“Now for ‘What we’d like to stop doing’ — things that slowed us down or created friction. Be honest; this is a safe space.”
“Finally, ‘What should we start doing’ — ideas for improvements we haven’t tried yet. New practices, tools, agreements.”
4Ls Format (Liked, Learned, Lacked, Longed For)
“For ‘Liked’ — what are you most satisfied with from this sprint? Not just what worked technically, but what felt good.”
“For ‘Learned’ — what did you learn this sprint? About the product, the codebase, each other, the process?”
“For ‘Lacked’ — what did you need but didn’t have? Resources, clarity, support, time?”
“For ‘Longed For’ — what do you wish had happened or existed? This is the aspirational category.”
Clustering and dot voting
After gathering inputs:
“I see a few themes emerging. Let me try to cluster these together — tell me if you see it differently.”
“Now that we’ve grouped them — we have time to go deep on two or three topics. Everyone has three votes. Dot vote on the topics you most want to discuss.”
“The top two themes are X and Y. Let’s start with the one with the most votes — does everyone agree?”
Facilitating Discussion
Inviting participation
“I notice we’ve heard from a few voices so far. I’d love to hear from everyone — does anyone want to add to what [name] shared?”
“Let’s hear from the quieter side of the room. [Name], do you have any thoughts on this one?”
“Before we move on — is there anything on this topic we haven’t said yet?”
Going deeper
“That’s an interesting observation. Can you say more about what that looked like for you during the sprint?”
“When you say the communication felt unclear — can you give us a specific example? It’ll help us make a more concrete improvement.”
“What was the impact of that on your work?”
Neutralising blame and generalisation
If a comment becomes blame-focused:
“I hear some frustration there. Let’s reframe: instead of focusing on who did what, can we talk about what system or process we could change to prevent this next time?”
“Let’s make sure we’re talking about patterns rather than individual incidents — what does this keep happening?”
Moving to Action Items
The retrospective must produce actionable, owned improvements — not a vague list of good intentions.
Transitioning to action:
“We’ve surfaced some great insights. Now let’s turn these into something actionable. For each improvement we want to make, I need: a clear action, an owner, and a target date.”
Asking for ownership:
“Who feels strongly about this improvement? Who would like to own it?”
“I want to avoid giving this to the same people every time. Is there someone who’d like to step into ownership of this one for the first time?”
Checking feasibility:
“Is one sprint enough time to implement this improvement? Or should we break it down further?”
“Let’s be realistic about capacity. We usually have time for two or three improvements. Which of these will have the most impact?”
Writing the action item:
“Let’s write this in a format we can inspect: ‘In the next sprint, [owner] will [specific action] by [date or sprint event].’ Does that capture what we agreed?”
Closing the Retrospective
Temperature check:
“Before we close — how satisfied are you with what we produced today? On a scale of one to five. Just quick hands or faces.”
Summarising commitments:
“Let’s review what we committed to: [read action items]. These will go into the next sprint board so they’re visible. Does everyone feel clear on their ownership?”
Closing line:
“Thank you for your honesty and energy today. These conversations make us a better team. See you at daily scrum tomorrow.”
“This was a great retro. The fact that we can have this conversation openly is itself a sign of a healthy team. Let’s go make it happen.”
Phrases for Difficult Retrospectives
| Situation | Phrase |
|---|---|
| Low energy / silence | ”It seems like the team is a bit drained today. That’s okay. Let me ask a simpler question: what was one small positive from this sprint?” |
| One person dominating | ”Those are great points. I want to make sure everyone has space — let’s hear from someone we haven’t heard from yet.” |
| Two people in conflict | ”I can see there’s some tension around this topic. Let’s pause and agree on the behaviour we want to explore, separate from the individuals involved.” |
| No willingness to commit | ”I notice we’re generating ideas but being careful about committing. What would make it safer to own one of these improvements?” |
| Retro going over time | ”We’re at the 45-minute mark. I want to make sure we leave with at least two clear actions. Can we agree on a top two right now?” |
Practice
Deepen your Agile facilitation vocabulary with the Scrum and Agile Coach exercise set and explore the full Scrum Master learning path.