Skip to content

Start with Trust, Start with a Retrospective

July 23, 2008 by Peter Stevens

Taking over responsibility for a troubled project is always a delicate situation. Something was not working as it should. There is a group of people in place, who may or may not 1) be working as a team, 2) have the necessary skills and a positive attitude, or 3) be willing to accept change. So how do you, the new project manager, get the team back on track quickly?

We all have our stories about arrogant consultants and managers who a) don't know the business, b) reorganize everything regardless of the consequences, c) quickly move on or get promoted, and d) leave the team to clean up the mess. A certain skepticism is not only to be expected, it is healthy. So the top priority is to win the support and respect of the team. A close second is getting the team working on improving the situation.

Scrum teaches a wonderful tool: the Retrospective, which is normally performed at the end of each Sprint. At the start of a project rescue, I like to use a Retrospective to get to know the team, identify short term action items, earn the trust of the team, and plant the seeds for transitioning to Scrum (while focusing on what the project needs, not on methodology).

Scrum implements Deming's Plan-Do-Check-Act Cycle and repeats the process at least once per month. I prefer to call it "Plan, Do, Review and Improve" because that's a better description of what actually happens. So for a challenged project, starting with the Improve step is actually quite a logical thing to do.

The Retrospective normally addresses 5 questions:

  • What happened?
  • What did we do well?
  • What could be improved?
  • Who has jurisdiction?
  • What is top priority?

In general, everybody who is directly involved in the project should be present, but no more than 15 people or so.

The result is two prioritized lists of action items to improve productivity in the project. The first list contains actions that the team can perform on its own authority. Items from second list require agreement from somebody 'outside', e.g. Management, the Customer, another department, whatever.

Why do a Retrospective?

By asking what happened, you build a common understanding of the project -- a common culture actually. Just getting people together at one table, giving them a chance to talk, and have them listen to each other goes a long way towards reducing emotional conflicts. You also send a message that what everyone has to say is important.

By asking what the team is doing well, you eliminate the risk of "throwing the baby out with the bath". You give everyone a pat on the back. You send the message that you understand that people are working for the good of the project and make clear that that is what people should be doing! They will respond and work better just because of the feedback and respect they are getting from you.

Furthermore, you have an opportunity to ask questions. "I would have expected pre-release testing would be high on the list of thing we do well. What testing do we do before delivering the software?" Either people will have a good answer or they are primed to make a good suggestion. By asking the right questions, you can drive the improvement process in the direction you want.

By asking the team how to improve, you get a list of short and medium term action items which will make visible improvements in the state of the project. Furthermore, the team owns the list, even the items you slipped in through clever questioning. So they will stand behind that list and help implement it.

By determining who has jurisdiction, you determine which items the team can action itself and for which items help or negotiations are needed. For the ideas under you team's control, they can start right away with the item at the first item on the list. For the rest, you start with the team's top priority request and work to get it approved.

Introducing code reviews might be an item on the first list: two developers get together and discuss their code. No one really has to even know, much less give their blessing. So just do it! Items on the second list may be difficult to get approved, and the chance of approval might play a role in assigning the priority. For example, you team might request a new build server. If you don't have the budget available, you would take responsibility for making it happen, and the team will love you when you are successful.

Some managers may be afraid that the team will come up with frivolous requests ("The whole team needs a fact-finding trip to Malta!?!"), but by prioritizing, you focus on what's really important. ("Yes it really does, and here is why..."). This is also why it is useful to have management present, so they appreciate the validity of the process.

The team may have enough ideas to keep them busy for the next two or three months, so you will probably need to focus on just a few items so that the team can continue to do productive work. Less important items can be postponed to the next retrospective.

Last but not least -- do it!

The consequence of every retrospective should be at least one concrete result — a list of things to do is nice, but you need actual results. When the team gets to do the things they've asked to do, that's positive reinforcement. When you make their top priority joint-responsibility request happen, you earn their trust and respect, which makes your life and theirs much easier.

But - If you don't allow them to do the things they identified, disillusionment can rapidly set in. So by the time you get to the next retrospective, you should have implemented (or least in the process of implementing) one or two of the top points from each list. Better to get one item done than to have 5 items in progress.

Results

My experience is that the team always identifies genuine potential for improvement (no one has suggested a trip to Malta yet). The top issues that arise out of that first retrospective are mostly organizational in nature and are easily addressed by introducing Scrum. This is the time to start talking to the team about Scrum and how it well help them solve their problems.

In the last year, I've been in involved in three rescues. Two were successful, one was not. In the latter case, the team identified much potential for improvement (some of it quite trivial to implement) but was not allowed to implement any of the changes they suggested, so the effort was stymied. Three months later, the project "hit the rocks," exactly as predicted during the retrospective.

One rescue, although successful, was started without a retrospective. The team reacted negatively and, despite objectively successful results, it was not until most of the old team members had moved on and been replaced with fresh blood that the mood turned positive.

The most successful rescue was started with a Retrospective. The team had the authority to implement most of the desired changes, so motivation, productivity and quality improved quickly and dramatically. Most of the issues raised by the team were addressed by Scrum or the tools we wanted to use, so acceptance of both was high from the beginning and there was no significant resistance to the changes in methodology.

How do you make the changes stick?

You won't change the world in one meeting. Emotional issues don't disappear in an afternoon. I remember one retrospective (between 2 "cooperating" companies) where the only agreement from the first retrospective was to have another one a month later. The trick is to make small improvements regularly. Emotional issues are often not "resolved" but simply dissolve over time. So repetition is important, especially when emotions are involved.

In an agile context, you would do a retrospective after every Sprint, i.e. once every two or three weeks. Even if you are not using Scrum or XP, retrospectives should take place a regular intervals no more than a few weeks apart. In any case, the top improvement on each list should be implemented (or at least under way) by the next retrospective.

Further Reading

There are many right ways and few wrong ways to hold the meeting. I like variations on Boris Gloger's Heartbeat Retrospectives. I plan to go into more detail about the retrospective meeting itself in a later article.

An understanding of Lean Principles and XP practices will help you ask good questions to the team. For a discussion of difficult project situations and the role of the retrospective, check out Saving Projects in Crisis on my blog.

About the Author: Peter is an independent Scrum Trainer and Coach. His mission is to help you realize complex projects. He provides coaching, training and project management to help you get started with Scrum, save projects in crisis and make your IT operations leaner and more effective.

Originally from the US, Peter now lives in Zurich. He studied Computer Science at Colgate University, started his career at Microsoft, and is now a Certified Scrum Master (Practitioner). He speaks English, German, French and Italian. An Instrument rated private pilot, his current hobbies are sign language and Sudoku.

Comments

Hi JamieThere are always

March 2, 2012 by NOnn (not verified), 2 years 26 weeks ago
Comment id: 21131

Hi Jamie
There are always great articles in HBR. It's one of the monthly subscriptions that I really look forward to reading. It will be interesting to see how the growth of agile intersects with the trend toward hyperspecialization. My first reaction in reading the article was. Uh-oh. this is very counter to what I like to do and do. And then looking at the process on TopCoder. that was very specific. waterfall steps. It will likely be years before we see what the result is. sosh forfait sans engagement forfait mobile illimite sms illimite forfait mobile internet comparateur forfait bloque rio bouygues numero rio orange rio sfr rio bouygues rio virgin imc portabilite du numero

An understanding of Lean

March 10, 2012 by sonymous (not verified), 2 years 25 weeks ago
Comment id: 21327

An understanding of Lean Principles and XP practices will help you ask good questions to the team. For a discussion of difficult project situations and the role of the retrospective, check out Saving Projects in Crisis on my blog.

fqxegktdi sa tacqpzekw hu iosagovvd

I agree that we should be

May 22, 2012 by JennyH811 (not verified), 2 years 14 weeks ago
Comment id: 22304

I agree that we should be careful not to overpromise. The agile principle people are refering to is continuous delivery
of valuable software'. The term business value is actually very broad and always up to the customer. An important part of agile software development is the discovery of what is actually valuable. The best way to do that is trying to improve the business process in small steps. One nice example is the roller skate example from Martin Fowler. I see it no so much as a promise. but a way of collaborating with the business. numéro rio

I like this type of post.

October 25, 2012 by Leave Module (not verified), 1 year 44 weeks ago
Comment id: 24279

I like this type of post. Thank you so much for sharing

If you don't allow them to do

January 15, 2013 by Anonymous (not verified), 1 year 32 weeks ago
Comment id: 25444

If you don't allow them to do the things they identified, disillusionment can rapidly set in. So by the time you get to the next retrospective, you should have implemented (or least in the process of implementing) one or two of the top points from each list. Better to get one item done than to have 5 items in progress.

katalog stron
katalog stron
katalog stron
katalog stron
katalog stron

Pretty good post. I just

January 30, 2013 by Anonymous (not verified), 1 year 30 weeks ago
Comment id: 26053

Pretty good post. I just stumbled upon your blog and wanted to say that I have really enjoyed reading your blog posts.
Perruques Femme perruque Perucken

Blogs Parcel || Blogs Phase

May 15, 2013 by sanatan (not verified), 1 year 15 weeks ago
Comment id: 27530

his article has me looking

June 2, 2013 by Anonymous (not verified), 1 year 12 weeks ago
Comment id: 28216

his article has me looking from the past and only now I found it. Improve the quality of your articles and continue to create a more interesting. Korek Api Gas Fighter Indonesia | Margahayuland

Extremely details

July 29, 2013 by make (not verified), 1 year 4 weeks ago
Comment id: 28467

Extremely details specifically the last part I care for such information and facts much. I was searching for this certain details for some time Wigs

I enjoyed reading you post.

July 29, 2013 by joson (not verified), 1 year 4 weeks ago
Comment id: 28468

I enjoyed reading you post. Usually writing skills is attained via practice: e. I am sharing it with my other friends on social networking sites, as the information is really very useful. Keep sharing your excellent work.Remy Tape Hair

Excellent article. Very

July 29, 2013 by francinegarcia (not verified), 1 year 4 weeks ago
Comment id: 28474

Excellent article. Very interesting to read. I really love to read such a nice article. Thanks! keep rocking. Learn More Here. -buy youtube views

I like this post. It's quite

September 3, 2013 by make (not verified), 51 weeks 6 days ago
Comment id: 28897

I like this post. It's quite unusual and innovative. Writer might be really gorgeous. Someone could easily claim that he is a genius. Superwatchus

I have not checked in here

September 10, 2013 by Anonymous (not verified), 50 weeks 6 days ago
Comment id: 29086

I have not checked in here for some time since I thought it was getting boring, but the last several posts are great quality so I guess I will add you back to my everyday bloglist. You deserve it friend
Media Informasi |Cara Memakai jilbab|FB Facebook|Status Lucu|Mengecilkan perut| Memutihkan Kulit|Menghilangkan jerawat| Menghilangkan Komedo |Ucapan Ulang Tahun

Membuat Twitter|Edit Foto Online|Contoh CV |Surat Lamaran Kerja|Kata Kata Lucu|Cerita Lucu|Kata Kata Mutiara|Depression Symptoms|Skin Care

I really adore your

September 11, 2013 by joson (not verified), 50 weeks 5 days ago
Comment id: 29147

I really adore your commitment to offer your readers such valuable information.Looking forward to read such informative content over and over again...Rolexforus

Soremi

November 13, 2013 by royal jelly nature's care (not verified), 41 weeks 5 days ago
Comment id: 30033

most of these reports hold represented performed on shiners and rest largely inconclusive. Royal Jelly Australia Review over the old ages, Royal Jelly is able to balance and order hormone tiers in the body.

This bus adventure seem to be

February 26, 2014 by Anonymous (not verified), 26 weeks 5 days ago
Comment id: 31393

This bus adventure seem to be relevant and interesting one. I think if there is touch of adventure in the bus tour then nothing can stop the rip to be exceptional one.
http://etnisjawa.blogspot.com/2014/01/agen-texas-online-indonesia-terpercaya.html
Agen Texas Online Indonesia Terpercaya
Alfamart official partner merchandise FIFA piala dunia Brazil 2014
Cipto Junaedy

192.168.1.1

March 7, 2014 by banite (not verified), 25 weeks 3 days ago
Comment id: 31929

I really get pleasure from

March 12, 2014 by Anonymous (not verified), 24 weeks 5 days ago
Comment id: 32060

I really get pleasure from this theme you've happening in your website. what's the name of the guide by the way? i used to be thinking of exploitation this vogue for the positioning i'm aiming to construct for my faculty project.Double Glazing Preston

Ogniwa fotowoltaiczne

April 14, 2014 by Waldek (not verified), 20 weeks 4 hours ago
Comment id: 32596

Na prawdę warto zastosować ogniwa fotowoltaiczne bipv ponieważ to dobre rozwiązanie na przyszłość i dla pokoleń budujących farmy fotowoltaiczne.

There are some people who

April 30, 2014 by Anonymous (not verified), 17 weeks 5 days ago
Comment id: 32846

There are some people who worry that the technological revolution and evolution we are experiencing today is moving too fast. There seems to be a loss of privacy in some respects and the specter of a Big Brother society looms larger than it has since 1984. www.fasatechnology.com

Learn what steps to take in

April 30, 2014 by Anonymous (not verified), 17 weeks 5 days ago
Comment id: 32848

Learn what steps to take in order to save money during a recession. Are there ways of saving money during a recession? Recession is a word that has a negative meaning for many people; it fills many people full of a dreadful fear of loss. People are scared that it means www.financialaidaudit.com

delightful blog

May 5, 2014 by Water purifiers in Chennai (not verified), 17 weeks 11 hours ago
Comment id: 32980

What a nice exposure carried throughout this blog which makes really organised to follow.
thanks for share
Water purifiers in Chennai

I like

May 12, 2014 by Friv (not verified), 16 weeks 16 hours ago
Comment id: 33222

thank for sharing

Hello

May 12, 2014 by kizi2 (not verified), 16 weeks 16 hours ago
Comment id: 33223

People are scared that it means

This was actually what I was

May 20, 2014 by eavedrop44 (not verified), 14 weeks 6 days ago
Comment id: 33243

This was actually what I was looking for, and I am glad to came here! Thanks for sharing the such information with us.Social Media Marketing Manchester

This is the kind of manual

June 14, 2014 by Anonymous (not verified), 11 weeks 2 days ago
Comment id: 33504

This is the kind of manual that needs to be given and not the random misinformation t hat's at the other blogs. Appreciate your sharing this best posting.Door Casing

Post new comment

The content of this field is kept private and will not be shown publicly.
  • Allowed HTML tags: <a> <b> <i> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd> <img> <br> <blockquote>
  • Lines and paragraphs break automatically.
  • Web page addresses and e-mail addresses turn into links automatically.
  • You can enable syntax highlighting of source code with the following tags: <code>, <blockcode>. Beside the tag style "<foo>" it is also possible to use "[foo]".

More information about formatting options

By submitting this form, you accept the Mollom privacy policy.

Best of AgileSoftwareDevelopment.com