As a project management expert, you know that: Lessons Learned meetings are an essential tool. Agile teams take this a step further. With agile retrospectives, you start thinking about the lessons learned and how to improve the collaboration even before the project is over – starting at the very beginning and continuing at regular intervals.
Such agile retrospectives aid the continual improvement of processes, methods, and teamwork.
This article covers the following topics:
- What is an agile retrospective?
- What should a retrospective include?
- How should a retrospective be organized?
- Which formats are best for holding a retrospective?
- Retrospective: methods and examples [+ downloadable template]
- Tools for virtual teams
- What happens after the retrospective?
Let us get started!
What Is an Agile Retrospective?
The basic concept of a retrospective is anchored in the 12th principle of the agile manifesto: “At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.”
Agile teams work in preferably short intervals called iterations (called “Sprints” in Scrum). These can be viewed as development cycles, but they also represent learning cycles because it is assumed that complex endeavors require a step-by-step approach in which it is necessary to frequently pause to evaluate oneself and the (intermediate) results. “Inspect & adapt” rituals are therefore a key ingredient of each iteration.
This gives you the opportunity to significantly influence the further course of your project. Three factors are analyzed and, if necessary, adapted:
The iteration review meetings or product review meetings with the stakeholders at the end of each iteration serve to evaluate and adapt the product. It also benefits the further development of its functionality, thanks to the stakeholder feedback.
What remains are the aspects processes and teamwork – which the agile retrospective meetings are designed to address. The retrospective is held at the end of an iteration, just as with the review.
Retrospectives thereby differ from the Lessons Learned meetings used in traditional project management, especially with regard to the timing and frequency. Projects planned in the traditional manner generally have the project manager meeting with the team when the project has concluded to discuss what happened and the lessons learned. With agile teams, this happens on a regular basis after each iteration – before the next iteration begins. This enables you to immediately apply what you have learned to the current project, instead of merely gathering these findings to use on some future project.
What Should a Retrospective Include?
Stakeholders can be invited to attend a retrospective meeting, but their presence is normally not necessary. If the team wants to speak openly and honestly about the iteration that just ended, having stakeholders present can be a hindrance.
Agile coaches (a “Scrum Master” in a Scrum Team) help the team identify good practices and possible improvements that can be used in the next iteration. A retrospective is therefore a joint team event – and experienced coaches always have a sufficient repertoire of formats to support this effort.
Candor and honesty are therefore essential in a retrospective.
Although the team might be quite satisfied with its accomplishments, with the team members congratulating themselves on a job well done, it is also important to be open about any critical issues and discuss these. This includes any feelings and emotions.
Provide a safe space for dealing with these.
At a minimum, the following people should participate:
- A Product Owner (or also a functional project manager, depending on how the team is organized)
- All other team members
- A team coach
How Should a Retrospective be Organized?
A retrospective typically takes up to three hours, depending on the length of the iteration being reviewed.
Experience has shown that a meeting with five phases is most effective:
- Provide an atmosphere conducive to discussions
The team meets for the retrospective. The participants strive to avoid distractions and agree to participate in an open discussion in which each person is treated with respect.
- Gather the issues to be discussed
Together, the team members reflect on how the iteration went and brainstorm ideas for possible improvements.
- Gain insights
All the participants delve deeper into the issues that were discussed: what were the causes? What specific steps can be taken to improve things?
- Reach decisions
As per the agile principle that “less is more”, the group agrees on 1-2 specific improvement measures to be implemented in the next iteration.
After reaching an agreement in phase 4, the retrospective is concluded, and the team members go their separate ways again. The next iteration can now begin.
Which Formats Are Best for Holding a Retrospective?
Generally speaking, no special format is necessary for holding a retrospective, with its individual phases, for your team. It is also not necessary to strictly follow each of the individual steps listed here, although the meeting generally quickly progresses from one step to another. The important thing is to end the meeting with an agreement on 1-2 specific improvements for the next iteration.
Experience has shown that the team often runs out of ideas and loses creativity after a few retrospectives. There is then an urge to abolish these meetings. Or the project team still has no idea how to ensure that the retrospectives are productive and creative.
For these situations, there is a wealth of formats and moderation techniques for engaging your team and making it easier and much more exciting for the team to work on improvement processes.
Our tip: A website with a trove of good ideas is Retromat: it provides formats for every phase of the retrospective. In the next section, we present a selection of these.
Please note: Teams generally enjoy trying these various techniques, but they can also be a bit overwhelming or exhausting. So, keep in mind that: less is more.
Experienced team coaches use 1-2 formats per retrospective. Some formats they repeat occasionally to avoid asking too much of the team. They sometimes completely omit one or the other a few times in between.
Choose the formats best suited to your team’s level of development or experience. The “starfish” is a classic format that is easy to use and understand and even works remotely if you use an electronic whiteboard.
For a format such as “Writing The Unspeakable”, on the other hand, you need a team that can meet undisturbed in a separate room and has members that know and trust each other well.
Our tip: Gently introduce your team to the latest retrospective techniques. Choose a rather simple format. Over time, you can progress to more demanding techniques.
Do many of the issues discussed deal with your environment in which the team works? If so, it makes sense to involve the stakeholders as well at some point.
You might also enjoy reading our blog article on agile contract models.
Retrospective: Methods and Examples
ESVP: Each team member is asked, in turn, which of these they feel like in today’s retrospective meeting:
- Explorer (eager and enthusiastic)
- Shopper (looks to see if any insights can be gained)
- Vacationer (enjoys the time off from other duties)
- Prisoner (would rather be somewhere else)
Each person writes the first letter of their choice on a piece of paper, and the papers are collected anonymously. If any of the papers show a V or a P, this is discussed. Why does someone feel like a “vacationer” or a “prisoner” in this meeting? What needs to change to improve the team’s attitude toward the retrospective?
Make a List of the Issues:
Sailboat / Motor yacht: The retrospective participants together view a picture of a boat on a flipchart or something similar and then, after writing the issues important to them on sticky notes, paste these sticky notes on the area of the picture they feel best represents their issue. Is the issue related to something that:
- Motivates us as a team (boat engine or sail)?
- Could present a future hazard (iceberg)?
- Is slowing the team down (anchor)?
Our download tip: Here is the template for holding a remote retrospective using the sailboat exercise. You can copy and use it for retrospectives with your team.
5 Whys: Originally developed by former Toyota CEO Taichii Ohno. Just as a child would do, we ask the question Why? five times. Let us look at an example.
Problem: We missed the delivery deadline for our new product version.
- Why did we miss the deadline?
- Because not everyone finished their tasks on time.
- Why was not everyone finished on time?
- Because there were a lot of urgent support requests to deal with at the same time.
- Why were there simultaneously numerous urgent support requests needing our attention?
- Because an important hardware update that was planned at the same time led to some bugs.
- Why was an important hardware update planned for the exact same time?
- Because the priorities for the team were not clearly set and planned.
- Why were the team’s priorities not clearly defined and scheduled?
- Because the stakeholders disagreed which was more important.
What caused the problem? Conflicting priorities among the stakeholders; the priorities were not coordinated well.
Taiichi Ohno believed the source of the problem would be pretty clear after the fifth “Why?” question. After doing this exercise, you can discuss the result and brainstorm ideas for avoiding this problem in the future. For example, it might be helpful to escalate the problem to the next higher level or help stakeholders reach an agreement.
Reaching an Agreement:
Using colored dots to vote: Present the measures suggested in the retrospective phases and then ask participants to vote on these using the colored dots they have been given. Each person is given two or three colored dots to allocate as they see fit to indicate the measures they deem most important. They can give all their dots to a single measure or distribute them among several measures. The measure with the most dots is implemented in the next iteration.
Concluding the Retrospective:
Respect and appreciation: Each team member is asked to personally thank or praise another participant for something specific that that person contributed to the project. It can be for help they gave or their strong commitment. After everyone has contributed, the retrospective can be concluded.
Tools for Virtual Teams
Some of the formats discussed above are intended for groups meeting in-person in a room. Project teams are increasingly global though and collaborating remotely. That does not preclude the use of innovative retrospective formats though.
In the retrospective, it helps to not only have a good videoconferencing tool (ideally with the webcams turned on so that everyone can see each other), but also the following tools:
- The website “Fun Retrospectives” has developed its own remote tool for the Starfish format.
- Interactive virtual whiteboards, such as IdeaBoardz, Miro, Mural, and Padlet, offer some templates for retrospectives. Team members can add their input to these boards in realtime.
- If you provide everyone involved with a set of Google slides or a Word file, you can use these together with the team members simultaneously and in realtime. Tables, sticky notes, etc. can also be used.
- For companies whose security policies prevent the use of the options mentioned above, you can simply create a presentation and share it directly from your screen. You can then add the team members’ feedback directly to this presentation so that everyone sees it right away. Another option is to email the presentation to the participants beforehand, which allows everyone to reflect on it and jot down ideas before the meeting. The combined feedback can then be further discussed in the meeting.
Possible templates for 3 and 4: the sailboat graphic in the figure above (downloadable directly below that figure).
Advanced Methods for Retrospectives
Is your team a group of experienced professionals already very familiar with retrospectives? If so, here are a few new other things you can try:
- Futurespectives, as the name suggests, lets you focus on the future instead of the past. This is especially useful at the project’s start when the goals and objectives are being defined and the risks are being identified. Possible formats that have proven successful are:
- Remember The Future – the team (possibly together with stakeholders and maybe a customer) is asked the question: “Assuming that the project just ended and was a complete success, what made it a success?”
- Pre-Mortem – Turning this question around to identify scenarios that you would want to avoid, ask the participants: “Assuming that the project just ended and was a complete failure, why exactly was it a failure? What caused the failure?”
- Hopes & Concerns – Everyone is given the chance to express their hopes and concerns regarding the project just starting, and these are then discussed with the other participants.
Another interesting read: TPG article on Agile Project Management Certifications
It is also enlightening to repeat an exercise such as this at the project’s halfway point to see what has changed since the project began.
- Liberating Structures was originally developed to act as a counterpoint to monotonous presentations ‒ “Death by PowerPoint” (too many slides with too much content) ‒ and endless meetings in which everyone just sits there waiting for them to end. It is a collection of formats designed to extract innovative ideas from the group by using the swarm intelligence of the group’s participants. This technique is useful in other areas as well but it works especially well in retrospectives.
Tip for beginners: 1-2-4-all: A topic is presented (to encourage more fun and creativity, the question can be formulated in a negative way. For example: “What is the best way to hamper our company’s agility?”).
- The team has 1 minute in which each participant writes as many ideas as possible on a piece of paper.
- Next, each participant selects a partner in the room. For the next 2 minutes, each pair discusses their ideas and creates a new, consolidated list.
- Afterward, each pair gets together with another pair. Each group of two pairs now has 4 minutes to discuss the ideas on their lists and create a new, consolidated list.
- In the final step, each group of four has 5 minutes to discuss and select the one idea that they find most important or concise to present it to the entire group later. Each group can write the idea on large index cards or a flipchart and then explain their idea to the entire group. Although the assignment was framed as a negative question, the ideas generated can then be reformulated as positive ideas.
Special Download: Agile, Traditional or Hybrid Project Management? (PDF file)
Please fill in the form.
* Required Fields | Data Protection
- Agile games are not only helpful for teaching agile methods in introductory workshops, but the gamification principle has also shown that formats using games and / or competition are more effective than discussions or presentations. They lead to a better long-term understanding of what has been learned. Familiar simulations such as Ubongo Flow Game, Lego4Scrum, and the Fearless Journey awaken participants’ playful instincts and function as direct, and often tactile, learning experiences.
Tip for beginners: White Elephant Sizing: The group estimates the work using T-shirt sizes as a reference. This gives the participants a feel for estimating the relative scope in agile projects. In a retrospective, you could ask the participants to start by estimating the amount of work involved in ordinary home activities (such as vacuum cleaning, decluttering a closet, renovating a kitchen, or cooking a meal) and then discuss within the team how each person arrived at these estimates. The insights gained can be used in the next iteration when it is time to estimate the effort involved in fulfilling “real” requirements.
What Happens After the Retrospective?
Ideally, your team comes up with at least one concrete, immediately implementable idea in the retrospective. It is important that the team actually implement this measure and that their efforts are taken seriously by those around them so that the team feels that the retrospective was worthwhile and productive.
You should therefore document these suggested improvements in a backlog.
Treat these with the same diligence as a functional or technical requirement in the next planning meeting: as something that must be planned and accomplished.
You can use metrics such as these to track the success of the implementation:
- Continual measurement of the productivity and number of tasks being handled simultaneously (team velocity)
- Reaching the target number of product users (customer surveys)
- Team satisfaction
- Team’s confidence in the quality of their product (employee surveys)
In this article, you have read about:
- Why you should not wait until the project is over to hold a Lessons Learned meeting, and how holding retrospective meetings regularly can help you gain insights into possible process improvements.
- Ways to ensure that your retrospectives are creative and productive in the long-term, including methods well-suited to remote and / or experienced teams.
- How to identify specific measures for improvement, implement these, and track their success.
- The role of agile coaches and Scrum Masters in assisting teams.
Please send us your feedback. What has been your experience with retrospectives and possibly with specialized methods? Can you offer any tips for working with remote teams? We look forward to hearing from you!
Author: Antje Lehmann-Benz (PMP, PMI-ACP, PSM expert / instructor in Agile Methodology)
Antje Lehmann-Benz, PMP, is a project management instructor with a special focus on agile issues and scrum seminars. She also has experience in providing software training (JIRA and Confluence) and consulting. In addition to instructing on frameworks and theory, she is also experienced in the use of agile games and practical exercises to reinforce the knowledge gained.