nuAgility Glossary
What is a Retrospective?
A retrospective is a structured meeting or process that is used to reflect on a past experience, project, or event in order to learn from it and make improvements for the future.
Retrospectives are commonly used in Agile development methodologies, such as Scrum or Kanban, as a way for teams to review their work and identify areas for improvement. However, retrospectives can be used in any setting where reflection and continuous improvement are valued.
During a retrospective, team members come together to discuss what went well, what didn't go well, and what can be improved for the next iteration or project. The focus is on learning from the past experience and identifying specific actions or changes that can be made to improve future outcomes.
Retrospectives can take various formats, depending on the goals, context, and team preferences. They may include facilitated discussions, brainstorming sessions, individual or group reflections, and other interactive activities.
The benefits of retrospectives include improved communication, increased collaboration, greater accountability, and a culture of continuous improvement. By reflecting on past experiences and making improvements, teams can work more effectively and efficiently and achieve better results.
While the agenda for a retrospective can vary depending on the specific needs of the team and the context of the project, a common agenda for an Agile retrospective typically includes the following items:
Setting the stage: This involves creating a safe and open environment for the retrospective and establishing the purpose and goals of the meeting.
Gathering data: This step involves reviewing the previous sprint or iteration and gathering information on what went well, what didn't go well, and any issues or challenges that arose.
Generating insights: In this step, the team analyzes the data and identifies themes or patterns that emerged during the sprint. This can involve group discussion and brainstorming.
Deciding what to do: Based on the insights generated, the team identifies specific actions or changes that can be made to improve the next iteration or project.
Closing the retrospective: This involves summarizing the actions identified, assigning ownership to each action item, and committing to making the necessary changes in the next sprint.
Some retrospectives may also include additional items, such as team-building exercises, individual reflections, or feedback on the retrospective process itself. The key is to create an agenda that allows for open communication, collaboration, and continuous improvement.
You want to learn more about how to do great retrospectives:
Why it matters
It gives a team a regular opportunity to learn from experience and change the conditions affecting its work.
Example
Consider a team repeatedly missing planned work because urgent requests arrive through several channels. In its retrospective, members gather recent examples, compare experiences, and identify an intake problem they can influence. They agree to test one visible request queue and a rotating person who handles initial triage, with a clear route for genuine emergencies. They assign ownership and choose to inspect interruption patterns and customer response at the next retrospective. The experiment reduces some interruptions but reveals an unclear escalation boundary, so they adjust it. Reflection leads to a specific change and learning, rather than a recurring list of complaints.
Common misunderstanding
A retrospective can become a recurring conversation that produces the same concerns and another list of actions. People may conclude that reflection is pointless when agreements are not carried into everyday work or the team cannot influence the causes it identifies.
Choose a manageable improvement and decide how to observe its effects. Revisit what happened, including obstacles outside the team's authority. Psychological safety matters, but avoiding every uncomfortable discussion also limits learning. A useful retrospective changes the next experiment or decision, not merely the meeting notes.
Related terms
Working Agreements · Kaizen · Agile Culture
Explore questions like this with other practitioners through the Agile Community Network, nuAgility's free live community event and podcast.