Retrospective Principles

This content is syndicated from George Dinwiddie's blog by George Dinwiddie. To view the original post in full, click here.

I’ve talked about the goals of a retrospective. Now I’d like to talk about four principles of effective retrospectives. I generally find that principles help me more to be effective while doing my work than do definitions. Principles help to connect the abstract to the actual practice.

One of the principles is that it’s important to understand the goals. If you don’t know where you’re going, any road will take you there. That road is, however, unlikely to be a retrospective. As a facilitator, I find the general goals helpful in planning a retrospective. I think that the specific goals are valuable to the participants, and generally discuss them as part of Setting the Stage at the beginning of the retrospective. As always, this is moderated by the understanding of the participants and the time available.

A second principle of retrospectives is that they are separate from ordinary work. While it’s certainly possible to notice things you want to change while you do your work, taking a look while doing nothing else will help you notice things you don’t normally see. Part of this difference is due to the sharpening your focus on observing rather than doing. When you are focused on doing, you suffer from “inattention blindness” in your observations. (See Daniel Simons gorilla experiment for an example of this.) Part is being more mindful about the variety of things you observe. You can choose what to observe, rather than let happenstance direct and limit your observations.

The third principle is perhaps the most important. A retrospective should build a shared picture. We do this by reviewing the past together. Different people notice different things, even when working together in the same environment. Different people notice different things when looking at the same event. And it’s likely that some people are not present for some events. Building a shared picture of the facts is crucial to a retrospective. It’s where the “retro” part of the term originates.

This shared picture of the past doesn’t mean that everyone agrees on what happened, or the significance of events. I don’t think it’s healthy for a group to take a homogenized view. The makeup of some groups can lead naturally to a very close viewpoint, and it seems to weaken the power of the group. Instead, it means that each person’s view is enhanced with knowledge about others views, whether subtly or dramatically different. Disagreement may be congenial or vehement, but the individuals can respect each other and live with their disagreement. This is healthier than denying a difference of opinion or remaining ignorant that it exists.

Finally, facilitation skills are necessary for a successful retrospective. Sometimes the group naturally has enough facilitation skills that things work out well, but that’s not the way to bet. It’s better if a retrospective is lead by someone who’s taken some time and effort to hone their facilitation skills. Of course, if everyone has facilitation skills, then they can make things easier on the leader of the retrospective. In a pinch, someone with strong facilitation skills can be a great help to a poor facilitator who is leading a retrospective. In general, though, it behooves the retrospective leader to be mindful of facilitation, and take steps to do a good job of it.

While I suspect that there are other principles that could be identified for retrospectives, these four seem essential, to me. When I’ve witnessed a weak retrospective, one or more of these principles has been violated. If you are leading a retrospective, I urge you to consider what ways you are following these principles.

Leave a Reply

What is 10 + 7 ?
Please leave these two fields as-is:
Please do this simple sum so I know you are human:)

There are 101 ways to approach anything.
To find the best way, sometimes you need expert help

What People Say

“Kelly revolutionised the way our digital department operated. A true advocate of agile principles, he quickly improved internal communication within our teams and our internal clients by aligning our business and creating a much enhanced sense of transparency in the decisions the business was making. Kelly also introduced a higher sense of empowerment to the development teams...”


“Kelly’s a leading program director with the ability to take charge from day one and keep strong momentum at both a program and project level driving prioritisation, resourcing and budgeting agendas. Kelly operates with an easy-going style and possesses a strong facilitation skill set. From my 5 months experience working with Kelly, I would recommend Kelly to program manage large scale, complex, cross company change programs both from a business and IT perspective.”


“Kelly is an extremely talented and visionary leader. As such he manages to inspire all around him to achieve their best. He is passionate about agile and has a wealth of experience to bring to bear in this area. If you're 'lucky' he might even tell you all about his agile blog. Above all this, Kelly is great fun to work with. He is always relaxed and never gets stressed - and trust me, he had plenty of opportunity here! If you get the chance to work with Kelly, don't pass it up.”


“Kelly is an Agile heavy-weight. He came in to assess my multi-million $ Agile development program which wasn’t delivering the right throughput. He interviewed most of the team and made some key recommendations that, when implemented, showed immediate results. I couldn’t ask for more than that except he’s a really nice guy as well.”


“Kelly and I worked together on a very large project trying to secure a new Insurer client. Kelly had fantastic commercial awareness as well as his technical expertise. Without him I would never had secured this client so I owe a lot to him. He is also a really great guy!”


“Kelly came to the department and has really made a huge impact on how the department communicates, collaborates and generally gets things done. We were already developing in an agile way, but Kelly has brought us even more into alignment with agile and scrum best practices, being eager to share information and willing to work with us to change our processes rather than dictate how things must be done. He is highly knowledgable about agile development (as his active blog proves) but his blog won't show what a friendly and knowledgeable guy he is. I highly recommend Kelly to anyone looking for a CTO or a seminar on agile/scrum practices - you won't be disappointed!”


“Kelly was a great colleague to work with - highly competent, trustworthy and generally a nice bloke.”


“Kelly was engaged as a Program Director on a complex business and technology transformation program for Suncorp Commercial Insurance. Kelly drew on his key capabilities and depth of experience to bring together disparate parties in a harmonised way, ensuring the initiate and concept phases of the program were understood and well formulated. Excellent outcome in a very short time frame. ”


“I worked with Kelly on many projects at IPC and I was always impressed with his approach to all of them, always ensuring the most commercially viable route was taken. He is great at managing relationships and it was always a pleasure working with him.”


“I worked with Kelly whilst at Thoughtworks and found him to be a most inspiring individual, his common-sense approach coupled with a deep understanding of Agile and business makes him an invaluable asset to any organisation. I can't recommend Kelly enough.”


“Kelly was a brilliant CTO and a great support to me in the time we worked together. I owe Kelly a great deal in terms of direction and how to get things done under sometimes difficult circumstances. Thanks Kelly.”