Here are 100 lines of ideas and phrases inspired by Diana Larsen and Esther Derby’s book Agile Retrospectives: Making Good Teams Great — practical insights and exact things to say when facilitating retrospectives effectively..
The goal of a retrospective is learning, not blaming.
Create a safe space before you ask hard questions.
Say: “Our goal today is to learn how to work better together.”
Start by appreciating what went well.
Begin with check-in questions like “What’s one word that describes this sprint?”
Use icebreakers to lower tension and spark openness.
Example: “What’s something you’re proud of this sprint?”
Remind everyone: “This is a judgment-free zone.”
Make safety explicit: “What’s said here stays here.”
Establish working agreements early.
Example: “Let’s listen fully before responding.”
Use a “Safety Check” to gauge openness.
Ask: “On a scale of 1 to 5, how safe do you feel to speak freely?”
Thank people for showing up honestly.
Set clear boundaries around time and focus.
Example: “We’ll keep this to one hour and focus on our process, not personalities.”
Explain why retrospectives matter.
“We pause to improve how we work, not just what we deliver.”
Reassure: “We’re not fixing blame; we’re finding patterns.”
A calm, clear tone builds trust faster than any exercise.
Look back at facts, not feelings first.
Example: “What happened this sprint that stands out to you?”
Collect data from multiple perspectives.
Use the timeline exercise to visualize key events.
Ask: “What surprised you during this iteration?”
Capture both highs and lows.
Example: “What moments gave you energy?” and “What drained it?”
Invite all voices, especially quiet ones.
Ask: “What patterns are you noticing?”
Use sticky notes or digital boards for visual clarity.
Example: “Add one sticky per observation, one idea per note.”
Encourage neutrality: “Describe, don’t evaluate.”
Keep the data objective before interpretation.
Example: “We closed eight stories, two rolled over.”
Compare metrics with team sentiment.
Ask: “What does this data tell us about our process?”
Look for outliers — they hold valuable insights.
Visualize flow, blockers, and cycle time if relevant.
Example: “Where did work get stuck?”
Summarize the key data points before moving on.
Move from data to meaning.
Ask: “Why did this happen?”
Use the “Five Whys” technique to explore root causes.
Example: “Why did the story take longer? Why again?”
Encourage curiosity, not judgment.
Ask: “What surprised or confused us about this?”
Identify recurring themes in behavior or process.
Example: “We often skip testing until the end — why?”
Use metaphors to deepen reflection.
Example: “If this sprint were a movie, what would the title be?”
Help the team see systemic causes, not individual fault.
Ask: “What part of the system makes this pattern possible?”
Explore both positive and negative deviations.
Example: “What did we do right when things went smoothly?”
Encourage shared ownership: “What did we as a team contribute to this?”
Look for learning opportunities, not perfection.
Example: “What can this teach us about our process?”
Keep discussions balanced between success and challenge.
Capture insights as actionable lessons.
Summarize: “So what we’re learning is…”
Turn insights into experiments.
Ask: “What one change would make the biggest difference?”
Keep it small — one or two improvements per sprint.
Example: “Let’s try pair programming for one story next sprint.”
Use SMART actions: specific, measurable, achievable, relevant, time-bound.
Prioritize improvements with team votes.
Example: “Dot vote for the top two actions you’d like to try.”
Avoid vague resolutions like “communicate better.”
Example: “We’ll hold a daily 10-minute sync at 9 am.”
Assign ownership to each action.
Example: “Sam will check in mid-sprint to track progress.”
Review impact regularly.
“We’ll revisit this experiment next retrospective.”
Focus on change, not perfection.
“We learn by trying, not by talking.”
Encourage optimism: “We can always improve one thing.”
Combine quick wins with deeper improvements.
Example: “Quick win: reorganize backlog. Deep change: reduce WIP.”
Ask: “What might get in our way, and how will we handle it?”
Close decisions with clear, written agreements.
Reflect on the session itself.
Ask: “How was this retrospective for you?”
Gather feedback on format and flow.
Example: “What should we keep, start, or stop in our retros?”
Celebrate learning and progress.
Example: “We discovered three new ideas and made one decision.”
End with gratitude.
“Thank you for being open and honest today.”
Recognize improvements, no matter how small.
“We’ve come a long way since last sprint.”
Use an appreciation round.
Example: “I appreciate Alex for jumping in to help with testing.”
Acknowledge emotional tone shifts.
“We started tense but ended collaborative — that’s real progress.”
Reinforce ownership: “These are our actions, not management’s.”
Schedule the next retrospective before closing.
Keep the loop continuous: inspect, adapt, repeat.
Capture notes and actions in a visible place.
Example: “We’ll post our improvement board next to the Kanban.”
Leave with energy and optimism: “See you next sprint, better than before.”