Sprint Retrospective phrases in English
A retro looks back at the sprint: what went well, what didn't, and what the team will change. It only works when people speak honestly without blaming anyone, and when it ends with a few action items that have an owner. These phrases help you do both. Fill in the “…” with your own ticket, name or date.
What went well
-
1
Something that went well for me was …
Opening your turn on a positive.
-
2
Shout-out to … for …
Thanking someone by name for something specific.
-
3
Pairing on … really helped.
Naming a practice worth keeping.
-
4
We should keep doing …
Turning a good thing into a habit.
What didn't go well
-
5
One thing I'd like us to improve is …
Raising a problem without blame.
-
6
What slowed me down was …
Talking about your own experience.
-
7
I don't think anyone did anything wrong; the process let it through.
Moving the talk from people to process.
-
8
This came up in the last retro too.
When a problem keeps coming back.
-
9
We found out about … too late.
A timing problem, said plainly.
Responding and disagreeing
-
10
I see it a bit differently.
Disagreeing softly.
-
11
That's fair. From my side, …
Accepting a point, then adding yours.
-
12
I hear you. Can we look at why that happened?
When someone sounds frustrated.
-
13
Can I add some context?
Before explaining what happened on your side.
Action items
-
14
As an action item, I'd suggest …
Turning a complaint into a change.
-
15
I'm happy to own that.
Taking an action item yourself.
-
16
Can we put a name and a date on it?
When an action item has no owner.
-
17
How will we know it worked?
Making an action item checkable.
-
18
Let's keep it to three action items, otherwise none of them get done.
When the list gets long.
-
19
Let's check on this at the next retro.
Closing the loop.
Common mistakes
Sentences non-native speakers often say in a sprint retrospective, and a more natural way to say them.
-
You said It's not my fault, the backend changed the API.
Better The API changed late, and we didn't have a check to catch it.
Describe what happened and the gap in the process, not who to blame.
-
You said The code review is so slow.
Better Code reviews took two to three days this sprint, which held up testing.
A number and an effect are easier to act on than a feeling.
-
You said We need to improve communication.
Better Can we post API changes in the team channel before merging?
Suggest one concrete change; improve communication can't be owned.
-
You said Everything is okay, nothing to improve.
Better Mostly smooth for me. One small thing: the test build came late on Friday.
There is always one thing; the retro needs it.
-
You said I'm so sorry for the bug.
Better That bug was on my ticket. Next time I'll add a test for that case.
Own it once and say what changes; a long apology makes others uneasy.