Professional Documents
Culture Documents
Retrospectives in 21 Steps
Based on original blog article at
http://www.improvement21.com/2015/09/02/21tipsforeffectiveretrospectives/
Retrospectives are a wellknown
improvement practice of many
effective teams across a broad
range of industries. They are a
key building block to
organisational improvement and
improvement habit building due
to their structured and periodic
nature. Essentially,
retrospectives are about
meeting with the people in your
team periodically – every two
weeks, for instance – in order to
analyze how the team is
performing. Performance can be
assessed and measured from
several perspectives:
Process
: Edward Deming said that bad process will beat good people every single time. There’s
also a popular saying in the Agile community: ‘Best practice is always past practice’. Although
several best practices can be valuable, they have to be understood as the current best practice.
Believing that there is no better way of doing something is against the very nature of continuous
improvement as a mindset and retrospectives as a practice.
People
: if you don’t have the right people, or they lack the skills needed in order to develop
great products, it is unlikely that your company will overperform its competitors. Even if you
have the right people on your team, you need to make sure that everyone is intrinsically
motivated to do their best contribution for the shared purpose of the team.
Teams
: even if you develop people’s competence, if they fail at creating effective teams your
company will also lack the desired performance level. You need to improve teamwork, both by
working with individuals (training, mentoring, coaching etc.) and with teams as a whole (team
coaching and facilitation).
Product:
next time you look at a failed product, ask yourself – what if the team creating this
product was the most productive and effective team ever? What if they were using all the Lean
and Agile processes, methods, practices and tools? The product would still be a failure, and
that’s probably because the company failed to identify a viable productmarket fit or a scalable
business model for growth.
Culture
and change : it is commonly believed that it was Peter Drucker who coined the
sentence “Culture Eats Strategy for Breakfast”. Most recently, Management Guru Jurgen
Appelo stated that “Management Eats Everything for Breakfast”. If we fail to change culture, it
will slowly revert to the initial status quo
that people identify as the default cultural identity as
soon as we stop pushing the change initiative. Forcing people to behave differently by using
coercive power is not organic, will only work while the authority is perceive, but as soon as
people perceive that there is no more energy injected into the change process, they will revert to
the original state. Again, only by creating a new culture and migrating people’s identity to the
new state can we make sure that improvements will stay in the long term with the organization.
In retrospectives, all these 4 dimensions Process, People and Teams, Product, Culture and
Change are analyzed and assessed. Bright spots things that work well today are identified,
and ways to enhance them and spread these practices to the rest of the organization are
discussed. Anything that the team identifies as an impediment – something that prevents the
team from achieving optimal performance – is also analyzed in order to design correction plans.
Again, impediments can be related to culture, process, people, teams or products. Teams need
to be careful that improvements have to be conceived from a wholesystemview principle, as
local improvements can often lead to poorer overall performance, a systemdynamics
phenomenon known as suboptimization.
There are two essential aspects of retrospectives that make them different to other kind of
improvement practices or events:
Empowered teams : instead of having a knowitall manager or an external expert, the team is
commissioned to analyze their own environment, identify the biggest improvement opportunities
and implement the changes that they think will contribute to a better performance. Managers
and experts will be available to assist them, facilitate their work, provide the resources or
remove the organizational impediments that are beyond the ability of the team, but at the core of
the retrospective practice there should be an empowered team that believes that continuous
improvement is their responsibility.
Short feedback loop : Yearly performance reviews or strategic planning exercises are
nowadays widely considered bad practices, and they are being replaced for smaller but more
continuous planning and mentoring exercises. In this line, retrospectives are typically conducted
every week or two weeks – although some teams are experimenting with even shorter feedback
loops, like daily halfanhour retrospectives. In general, modern companies operate in
environments that are so complex that waiting too much in order to solve a problem can derive
in catastrophe.
Retrospectives are a very effective way to introduce improvement habits at your organization,
starting at the team level. Neuroscience (The Power of Habit, by Charles Duhigg) has found
that, in order to create a habit, four things are necessary:
Cue
: something needs to trigger the habit
Behavior
: the desired behavior is performed
Reward
: after the behavior, certain reward is obtained
Persistence and craving : after several repetitions, the brain learns to crave the reward
and looks for cues in order to perform the behavior
For instance, many people in several cultures have a midmorning breakfast habit. The cue is
usually a given hour, or some of their work colleagues standing up and walking towards the
office cafeteria. The behavior is having some coffee and maybe a snack. Both caffeine,
snacking and slacking excite their brain’s pleasure circuits, so after several repetitions these
people develop a midmorning breakfast habit – almost an addiction, in the sense that now, if
they can’t get their breakfast, they suffer from weaknesses, dizziness and bad temper – while
other people, who haven’t developed the habit and have not had breakfast too, are not suffering
these symptoms.
How can we use retrospectives to introduce an improvement habit?
Cue : retrospectives are held at the
end of every week or twoweek work
cycle (usually referred to as an
‘iteration’), at the same time.
Reminders are in place to invite
attendees.
Behavior
: a predefined process
is conducted. As described in “Agile
Retrospectives” by Diana Larsen and
Esther Derby, it usually includes
defining the context, gathering data,
generating ideas, planning what to
improve and closing the retrospective.
Reward
: learning, improving and
celebrating our performance can be
some obvious rewards you can get out of retrospectives. Others include team interaction, a
sense of autonomy or even reinforcing the team purpose and values.
Persistence
& Craving : once several retrospectives have been conducted and they have
provided proper rewards, the practice becomes an improvement habit in the organization and
people are looking forward to discuss relevant items at the next retrospective.
Different kind of retrospectives:
Most Agile teams are conducting retrospectives at the end of every development iteration
typically every two or three weeks just after the iteration review or “demo”, where an increment
of working product has been presented to the customer. The review focuses on the “what”
what has been delivered, what’s missing, what’s right, what can be improved whereas the
retrospective features the “how” how have we collaborated, how can we go faster, how can we
remove impediments, how can we work better as a team…
Besides the “typical” endofiteration retrospective there are a series of special improvement
events that can also be considered retrospectives and benefit from the tips discussed in this
document:
PostMortem retrospective : a widespectrum retro, this particular kind of event focuses on a
medium to big project as a whole. The postmortem tries to capture best practices and lessons
learned at the end of a whole endeavour or period.
Crossretrospective : the purpose of a crossretrospective is to gain new insights and to improve
collaboration and knowledge sharing between teams. One way to run a crossretrospective is to
involve members from multiple teams and parts of the company, to reflect on collaboration and
common issues between those teams. Other way to do a crossretrospective is to switch
facilitators for the event between teams. A new person will bring in new ways to facilitate the
event that may lead to useful, new outcomes for the team. A third way to run a
crossretrospective is to have each team reflect on some other team’s issue and propose
possible solutions. This way, the emotional layer and biases can be taken out from the process
that the other team facing the issue right now might have.
Focus retro : a focus retrospective might be useful when a team is facing a big, hairy issue that is
difficult to resolve. The issue can be cultural, teamwork related, a role or any other impediment
that may stop them from doing their job at their best. In this case, the team chooses to focus on
just this topic and often bring in some help experts, senior facilitators, relevant stakeholders
to address the issue.
Timeline retro : the timeline retrospective can be helpful to recall main series of events along a
timeline with all relevant stakeholders involved. For example if a team has just made a key
release deadline, but it was very tight, they might choose this format to reflect on the story of
how they planned, collaborated and improved along the timeline of the release. Some teams
use visualisation of the timeline, happiness indicators and key events (including failures and
improvements) to share stories of what happened, why and what they can learn from it.
Community retro : many Agile companies have adopted crossfunctional teams as their
fundamental organizational paradigm. Lean Software Development expert Mary Poppendieck
defines this teams as “full stack”: each team will have enough components and knowledge to
push a full feature from concept to production with no external dependencies. In such a team is
easy to find both business analysts, developers, testers or infrastructure experts working
together. Hence, each professional profile will communicate and synchronize with their peers
through communities of practice, sometimes referred to as “tribes” or “guilds”. A community retro
will feature one of these communities the testers community, the designers community and
will focus on the specific topics of this group.
All hands retro : this is a fullcompany event, an opportunity to be open and build trust,
communication and collaboration all across the organization. With the appropriate facilitation
and space, we’ve seen up to 300400 people collaborate effectively into creating a prioritized list
of organizational issues that they’d like to be addressed.
Meta retro : The purpose of the meta retrospectives is to essentially evaluate and reflect on the
retrospective process itself. On this meeting, team members discuss what elements of the
process work well and generate improvement results while what elements need adding or
finetuning. Experimentation trying new things out and evaluating at the end is key to
finetune your retrospectives. You can start experimenting with the contents of this whitepaper
to improve your retrospectives and evaluate things to keep, add, modify on your next meta
retrospective.
Open Space 1
: open space is an emergent conference organization system, sometimes referred to
as “unconference” in the sense that there is no predefined agenda. Participants will show up,
propose topics, vote on them and the most voted will be hosted on sessions by the same people
that proposed them. As a topic host, you don’t have to give a lecture or be the subject matter
expert: just make sure that the session starts on time, stays on topic and ends when it’s
supposed to. Open Space format can be a good way to facilitate large group retrospectives or
even to explore what are the main concerns of a given team and develop their engagement.
1
Learn more at http://openspaceworld.org/wp2/
Retros gone wrong
Unfortunately, many teams have tried retrospectives and have found them boring, dull and
unproductive. According to our experience, several things can go wrong when facilitating a
retrospective, and if these are not addressed, teams might lose interest in retrospectives
completely.
Some of the most common retrospective “failure modes” include:
Groundhog day retrospective : the same retrospective happens over and over. Same issues are
discussed, same impediments detected and then… Nothing happens. The problem here is a
lack of effective planning and followup.
Whining retrospective / too negative retrospective : retrospectives become a place to complain
and whine about all things that go wrong. This will lead to no action and negative experience.
Proper facilitation and appreciative inquiry methods such as the solutionfocused retrospective
[see the end of this paper] might solve this problem.
Blaming retrospective / people affected /
personally offended:: people tend to blame
each other or even worse people that are
not in the room for the failures and
impediments. This is a typical symptom of
weak team identity, poor collaboration or
failed culture. The facilitator should try to
emotionally deescalate any existing conflict
and focus on facts rather than opinions.
Nonviolent Communication2 could be a good
resource for such a situation.
Playground retrospective : the time is
spent playing games, teambuilding
exercises and icebreakers. Usually the
problem is a lack of understanding of what a retrospective should be and the expected results.
Following the tips proposed in this document should give some clues on how to move on from
this failure mode.
2
https://en.wikipedia.org/wiki/Nonviolent_Communication
Low interaction / participation : nobody talks, or only few people talk. Again, this could be both a
weak team symptom or a lack of understanding of the retrospective mechanics. Trust issues
should be addressed individually out of the retro using coaching techniques. Participative
games or dynamics can help to involve everyone in the team.
Not enough time : teams who just dedicate few minutes to retrospectives usually suffer from a
bad understanding of their role in the organization’s continuous improvement. Another typical
reason for too short retros is that no results are ever perceived out of them, so the team just
conducts retros as part of their “conformance to the given process”, a form of cargo cult3.
Finally, sometimes the problem is that there is enough time but this time is poorly managed.
Managers, team facilitators and improvement agents must make sure that the team dedicates
quality team to their retros and that they see the results afterwards (cuebehaviorreward).
Proper facilitation is always a powerful tool when it comes to effective retros.
Retrospective hijack : someone uses the retrospective time to vent out, talk about something
else or promote a personal agenda. This is more a moderation issue than a facilitation one. The
team facilitator should not boss the team around, but some amount of discipline and authority
might be required in order to be effective. Personal coaching of the hijacker after the meeting is
advised do not address personal issues in a group meeting unless you are sure that the team
has an offthecharts internal vulnerability and trust level!
No problem / no causes : team fails to see improvement opportunities. If no problems are
identified, the team facilitator should make sure that they are spotted and noted down on a daily
basis so we get to discuss them on the retrospective afterwards. Even if the team sees no
impediments, they can also be asked if there’s something they are doing right that can be
maximized. On the other hand, sometimes the team identifies impediments but can’t see how
they can do something about it. In these cases, root cause analysis, causal diagrams and other
problemsolving techniques can be useful.
Artificial harmony : team does not wish to discuss conflictive issues. Unfortunately for them,
certain constructive and positive level of conflict is not only desirable, but even necessary in
order to advance and mature as a team. A proper and agreed consensus process can help
teams dive into conflict with more confidence; again, introducing nonviolent communications is
always a great help for teams to navigate conflict.
No diffusion of best practices or lessons learned: team fails to spread their actions and
knowledge to other teams. Publishing the retro results using information radiators or wiki pages
is a good way to improve this issue. Team facilitators also have a key role in spreading good
practices and lessons learned. Crossretrospectives can also be a good choice if this problem is
detected.
3
https://en.wikipedia.org/wiki/Cargo_cult#Metaphorical_uses_of_the_term
Too many actions : the team decides to “bite off more than they can chew”. Prioritizing issues,
breaking them in small experiments and keeping a “work in progress” limit (WIP limit) on the
number of improvements can effectively solve this problem.
Weak plans : team decides to go for an issue, but fails to decide on specific actions, responsible
name, approaches, strategies… For instance, the team decides to “increase collaboration” but
fails to specify how exactly are they going to do that. Strong plans will at least define what’s
going to be done, who is going to take care of it, when it’s going to be done and how exactly.
If one or several of this failure modes is present long enough, the retrospective habit might
never be acquired. If we review the cuebehaviorrewardcraving cycle, we can figure out why
retrospectives might not be permeating the organization’s culture:
Missing Cue : a common mistake to postpone your retrospectives when your team says that they
are ‘too busy’ or behind for an important deadline. When will you improve and learn if you don’t
allocate time for it? Another common situation is to keep changing the location and time of your
retrospectives or sending out invitations for the meeting last minute to participants. Make sure
you create a stable, consistent cue for the start of the retrospective for all involved.
Inconsistent Behavior : the previous failure modes gave plenty of examples on how to make
retrospectives fail by focusing on the wrong things, going in unprepared or missing to agree on
next steps after the meeting. For improvement habits to build, we need to create an effective
retrospective process that leads to positive, noticeable rewards. We recommend that you vary
your meetings and activities but follow the structure recommended by our 21 step improvement
process.
No Reward : a badly prepared or run retrospective process will inevitably destroy the intrinsic
motivations for people to take part in it. If people are not involved, heard and not learning, you
are missing out on creating rewarding reasons to attend the event. Avoid using retrospectives
simply as a status reporting tool for upper management or yourself. Also, be careful not to forget
celebration and appreciation as key rewards for all team members. Celebrating key team
achievements, improvements, milestones and saying thank you to your peers and contributors
are great ways to reward and entice people to keep participating in improvement events.
Lack of Persistence and Craving : the failure to create a rewarding experience with retrospective
in itself is enough to stop people wanting to go to such events. Another failure mode is to skip
retrospectives or to mix up their schedule so they become unexpected and unreliable. Both of
these situations can stop teams from using regular, effective retrospectives as a way to improve
their work and environment.
Improving Your Retrospectives
After analyzing these failure modes, we designed 21 simple steps to enhance your
retrospectives and to help you prevent bad behaviors from killing the improvement habit in your
company.
Following these 21 simple tips you will have better chances that your retrospectives – or any
other kind of improvement event you are facilitating – become an exciting event that your team
will see as a natural and useful way to improve everything.
1. Prepare : or as we sometimes say, ‘don’t show up naked’. Take notes during the week in order
to have something to discuss at the retrospective. Bring data, reports, emails or whatever you
need in order to review what has happened during the last two weeks (or whatever the
retrospective frequency is).
2. Test the waters : Test also the mood of the participants – sometimes it’s just not the right
moment for reflection.
3. Facilitate and moderate : a good retrospective needs moderation – making sure people stick to
the rules and listen to each others – and facilitation – maintaining the team engaged through
questions, activities, dialogues and dynamics.
4. Have someone taking notes – all the facilitation and moderation activities will require 110% of
your attention. Many things will be forgotten or even missed unless someone helps you taking
note of comments, issues, attitudes…
5. Set up : Make sure you have enough space and that there’s intimacy and trust, so people are
open to talk about anything that worries them. Make sure everyone understands the goal of this
meeting – which is not blaming people, but seeking new ways to improve.
6. Involve everyone : a first round of questions where everyone has to contribute is a good way to
make everyone check in. No matter how you do it, make sure all voices are heard.
7. Remember: start by reviewing all the commitments the team made during last retrospective and
see if there has been action towards them. If the team forgets their improvement plans after the
retro, that’s a major problem you need to address before anything else.
8. Review improvements : for each commitment the team worked on, try to analyze the results.
Did it make a difference? Can we make more of it? Shall we continue trying or should we try
something else?
9. Tell the story : storytelling is a powerful technique to connect with people and trigger insights.
Instead of jumping into problems, try to recover the story of the last two weeks, day by day,
event by event.
10. Pluses and Deltas
: during the story, take notes of the bright spots and the improvement areas.
11. Experiment : don’t focus only on “We did this wrong” or “We did this right”. Some things we
haven’t tried. Try to come with suggestions of things we might just try and experiment with.
12.Don’t go too deep yet
: it’s easy to get trapped by some of the things that arise.
13.
Prioritize and Divide : some teams try to chew more than they can swallow. Try to find things
you can work on that have a high impact on the team but, at the same time, are feasible to be
addressed by the team.
14.
Make a break : a retrospective can be exhausting. Consider making a break or playing some
funny, energizing game.
15.
Root Cause Analysis : once you have decided what are you going to improve next, try to work
on the causes of this behavior. Try to understand the reasons this happens, and make sure you
don’t treat symptoms instead of causes.
16.
Plan for success : many teams fail because
they commit to fuzzy, nonactionable goals like
“we are going to focus more on productivity”.
Try to define what exactly are you going to do,
when are you going to do it, who is going to do
it and how is he or she going to do it.
17.
Visualize your plan : People create a shared
understanding much better when they not only
say things but also see and draw them. Use
our Improvement21 retrospective grid and
draw it, customise it to your taste to visualise
your improvement plan and next actions.
18.
Celebrate : in some cases, retrospectives
fail because they become a review of
problems and uncomfortable situations.
Try to keep the retrospective positive and
improvementfocused. Close the
retrospective asking people to thank their
peers for specific things they’ve done
recently that helped them improve.
19. Retrospect the retrospective : spare
some minutes at the end of the meeting
to ask everyone to rate the retrospective
and suggest how can next retros be
improved.
20.
Publish your retro : make sure all your
findings, commitments and appreciation
notes are available to see by everyone else in the company to inspire them. This also puts
some peer pressure in the team to deliver on their commitments. I’m a fan of visual
management – crafting a simple handdrawn poster with all this information and hanging it on
the team area – but you can also use electronic tools if they work better for you.
21.
Follow up : until the next retrospective, make sure people review the improvement plan daily
and help them stay focused. Urgent stuff will always be around – e
specially if we never improve!
Bonus 1: Solution Focused Retrospective
‘Problem talk creates problems’ : don’t focus too much on the negative side of impediments and
problems. Focus the retrospective discussions on solutions, alternatives and options instead.
You can use these ten questions to go over any impediment and design action plans with the
team together. Alternatively, you can use this script on oneonone coaching sessions to move
improvement ideas to next steps and actions. Use ‘What else’ and other exploratory formulas to
solicit the less obvious answers and preconceived ideas.
The Facilitator’s Script:
1. What do you want to talk about that
is useful for you?
2. What is the goal to reach?
3. If you already reached our goal,
which effect would it have on you? Which
else?
4. When you reach your goal, how
would it affect others? And how else?
5. From 0 to 10, where do you see
yourself about reaching this goal now?
6. What did you already do so you are
at X and not lower? What was YOUR
contribution? And what else?
7. When you move up just one point, what differences would you notice? And what else?
8. What would YOU do differently when you are one step further on the scale? And what
else?
9. How would OTHERS notice that you are already one step further? And how else?
10. On a scale from 0 to 10, how confident are you that you will make this step? How could
you become more confident?
Bonus 2: Conflict resolution facilitation
If emotions are addressed correctly, this Conflict Resolution script can be used by a facilitator to
focus the conflict conversation on agreement and negotiation instead of just each person
defending their point of view.
Try to explore each question beyond the evident, immediate answer. Use open questions like
“and what else?” or “how else?”. “Why” / “How” (Root Cause Analysis) is also a powerful way to
deepdive into questions and find hidden issues.
The Facilitator’s Script:
• What’s the conflict we are trying to solve?
• What are the options? Which is the currently decided option?
• What’s the part of this option that you can’t live with?
• Is it an emotional issue or is it a factbased argument?
• How is this option personally affecting you?
• Why do you think other people might prefer this option?
• Is there any way we could modify this option so you could live with it, even if you don’t
fully agree with or like it?
• What other options can you provide? How are they different from this one?
• Can you support a timeboxed test of this option?
What is improvement21?
www.improvement21.com
We started
improvement21
because we believe that improvement is everyone’s daily job. For
companies to strive, everyone on the team needs to have the tools and means to influence
where they are going and how things are getting done. We are doing this because we believe
that people should be happy at work. Happy people can change the world and create amazing
solutions!
We are Happy Melly Funders – check us out at www.happymelly.com!
Angel Medinilla and Andrea Darabos Improvement21 Founders
Sign up to our newsletter to receive our backstage news, whitepaper
releases and useful templates!
Or, do you prefer facetoface practice? Join one of our upcoming
improvement21 workshops!
We run events from South America, to Europe
to Israel check out our schedule on our website!