{"id":5272,"date":"2013-04-02T08:23:17","date_gmt":"2013-04-02T08:23:17","guid":{"rendered":"https:\/\/www.bridge-global.com\/blog\/\/?p=5272"},"modified":"2025-04-29T07:10:37","modified_gmt":"2025-04-29T07:10:37","slug":"agile-retrospectives-an-effective-tool-for-continuous-improvement","status":"publish","type":"post","link":"https:\/\/www.bridge-global.com\/blog\/agile-retrospectives-an-effective-tool-for-continuous-improvement\/","title":{"rendered":"Agile Retrospectives, an Effective Tool for Continuous Improvement"},"content":{"rendered":"

Most teams that are doing agile development and are using Scrum have heard about agile retrospectives. Often they also start doing retrospectives after one or more sprints. Some teams keep on doing them, but I\u2019ve heard a lot of teams that didn\u2019t do them frequently, or stopped doing them after some time. The reason I hear most is that they are not getting enough benefits out of them. But if not doing retrospectives means that you will not improve your way of working, and adapt to changes in your team or in your organization, that may be a high price to pay? My suggestion: Do your retrospectives!<\/p>\r\n

Are retrospectives difficult? No! Are they valuable? Certainly! But you have to know how to do them, to turn them into an effective tool for continuous improvement.<\/p>\r\n

Why do Retrospectives?<\/strong><\/p>\r\n

Let\u2019s first start by understanding why you would want to do them. The Agile Manifesto<\/a> provides us with a couple of good reasons. It starts with the first sentence of the manifesto:<\/p>\r\n

\u201cUncovering better ways\u201d tells me that there isn\u2019t 1 solution, not 1 best way, or silver bullet to do software development<\/a>. And since we are uncovering it, we will have to try things and reflect to see how it works. This is where retrospectives come in, as a way to reflect at the end of the sprint to see how the team has been doing their work. And to uncover what worked, and what didn\u2019t. Having an agile mindset means that you want to reflect and learn, and keep on reflecting and learning. You\u2019re never done!<\/p>\r\n

And then there are also the principles behind the Agile Manifesto<\/a>. The 12th principle says: \u201cAt regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.\u201d<\/em> It is often called \u201cinspect and adapt\u201d, which start by doing things, learn, and improve along the way. Just like you don\u2019t know all requirements up front when you start developing a product, you start working with what is clear and needed and then change based upon the feedback. Retrospectives are a way to \u201cembrace change\u201d in the way you work as a team.<\/p>\r\n

Retrospectives aren\u2019t something that agile or Scrum has invented. Getting feedback to improve yourself is much older. Actually, even project management methods like Prince-2 and the PMBoK has reflection included in the way that they propose to manage projects. What Scrum has done is to define a ritual to do the reflection, and to give it a clear spot in the software development cycle.<\/p>\r\n

How to do Retrospectives<\/strong><\/p>\r\n

So now that we understand why to do retrospectives, let\u2019s discuss how to do them. What I have found to be very important in having effective retrospectives is that the right culture is set at the start. I use the Prime Directive to assure that a retrospective is a positive and fruitful event. It states: \u201cRegardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand\u201d<\/em>. With the Prime Directive, a retrospective becomes an effective team gathering to learn and find solutions to improve their way of working.<\/p>\r\n

In a retrospective, a team reflects on their way of working. There are a lot of different techniques that can be used to do retrospectives, varying from asking questions with post-its to gather and organize the answers, building a timeline, root cause analysis to gaming (see Getting Business Value out of Agile Retrospectives<\/a> which describes many of them that I have used in retrospectives). Depending on the situation at hand and what the team would be looking for, I usually pick a technique that would be suitable.<\/p>\r\n

A technique that I use often is <\/strong>to ask \"the four key questions\":<\/p>\r\n