Say it like this
- Let's run a retrospective on this sprint
- In the retrospective, we discussed deployment issues
- I will facilitate the retrospective tomorrow afternoon
Use it at work
Running it
- What went well this sprint?
- What should we change next sprint?
Following up
- Let's pick one improvement from the retro.
- Who owns the action items from the retrospective?
Planning
- The retrospective is Friday at 2.
- Let's try a new retro format.
Don't say this
Retrospective is a noun referring to a meeting, not a verb meaning to review or examine.
Don't mix it up
| Term | What it is | Who writes or uses it | When |
|---|---|---|---|
| retrospective | Regular review of how the team works | Agile team | End of each sprint |
| post-mortem | Review after an incident | Engineers | After outages |
| debrief | Quick talk after an event | Anyone | Right after |
Practice
Try it
4 quick exercises
1. Your team just finished a two-week sprint. What do you say?
2. In our last _______, the team agreed to improve communication during deployments.
3. Which sentence uses retrospective incorrectly?
4. Rewrite this using retrospective: We will sit down as a team and talk about what we did right and wrong in the last two weeks.
Say it out loud
Phrase 1 of 3
"Let's run a retrospective on this sprint"
We don't save your recording. The word check uses your browser's speech recognition.
More about retrospective
Real examples(3)
- in a sprint planning meeting
"Before we start the next sprint, we need to hold our retrospective to review what happened last week."
- in a team message
"The retrospective is scheduled for Friday at 3 PM. Please come prepared to share feedback."
- in a manager conversation
"During retrospective, the team mentioned that unclear requirements were slowing us down, so we adjusted our process."
More mistakes(2)
Handle with care. Do not use as a verb (you cannot retrospective something). Do not confuse with retrospect, which is a different word. Avoid using it to mean simply looking back without a structured meeting context.
- ✕The retrospective should focus on individual mistakes.✓The retrospective should focus on process improvements and systemic issues.
Retrospectives are for identifying team process improvements, not for blaming individuals or assigning fault.
- ✕We had a retrospective last month so we do not need another one.✓We should hold retrospectives at the end of each sprint, typically every two weeks.
Retrospectives are regular, recurring meetings held after each sprint or project cycle, not occasional meetings.
Other forms(3)
- retrospective noun
"The retrospective revealed that our testing process needs improvement."
- retro (shortened form) noun
"Let us grab coffee after the retro to discuss the feedback."
- retrospective adjective
"We conducted a retrospective analysis of the project timeline."
Often used with(5)
- hold a retrospective · To conduct or schedule a retrospective meeting: We will hold a retrospective next Friday.
- run a retrospective · To facilitate or lead a retrospective: Who will run the retrospective this sprint?
- sprint retrospective · A retrospective held at the end of a sprint: Our sprint retrospective identified three action items.
- in retrospective · Looking back after the fact: In retrospective, we should have communicated more clearly.
- retrospective feedback · Feedback gathered during a retrospective meeting: The retrospective feedback was constructive and helpful.
Similar words(4)
- retro · Informal shortened version of retrospective, commonly used in tech teams.
- debrief · A general term for reviewing an event, but less specific to Agile processes.
- post-mortem · Similar structure but typically used after failures or incidents rather than routine sprints.
- lessons learned session · Broader term for extracting knowledge from past work, but may be less structured.
Opposites(2)
- prospective
- forward-looking planning
Questions(5)
- What does retrospective mean in software engineering?
- A retrospective is a structured team meeting held after a sprint or project phase to discuss what went well, what did not go well, and what improvements should be made. It is a core Agile practice focused on continuous team improvement.
- How often should a team hold retrospectives?
- Most Agile teams hold retrospectives at the end of each sprint, typically every one to two weeks. The frequency depends on the team and organization, but regular retrospectives are essential for continuous improvement.
- Is retrospective formal or informal?
- Retrospectives are usually semi-formal. While they are structured meetings with a clear purpose and facilitator, they are often conducted in a relaxed, open environment to encourage honest feedback. The tone should be professional but comfortable.
- What should be discussed in a retrospective?
- Retrospectives typically cover what went well, what did not go well, and what the team should do differently next time. Common topics include communication, processes, tools, team dynamics, and technical challenges. The focus should be on improvements, not blame.
- Can retrospective be used as a verb?
- No, retrospective is a noun in tech terminology. Do not use it as a verb like retrospective something. Use words like review, analyze, or discuss instead.
