Agile Retrospectives: The Preventative Medicine

One of the features of using Agile methods is the opportunity for continuous improvement within a project. There are a number of improvement opportunities throughout a typical iteration or sprint─over the next few weeks I’m going to walk through a few, starting this week with the Retrospective. Retrospectives are one of the many tools in Scrum and other Agile methods that are absolute must-haves for continuous improvement.

Think about the last time you built a product (or had one built for you). If you weren’t using an Agile method like Scrum, chances are that you pushed through the project in one big rush, waiting until the end to think of the things you would do differently next time. If you were lucky there may have been a chance for a review afterwards.

Enter the retrospective. Retrospectives take place frequently, at the end of every sprint (typically 2-4 weeks), and give the team a big opportunity to do things better sprint by sprint. A retrospective helps the team identify any changes or corrections needed during the project.

While I’m a fan of a good post-project review it is often equated to a post-mortem and, following this analogy through, retrospectives are closer to the idea of preventative medicine. Ultimately this isn’t so different from any other lessons learned process but for me the frequency and drive for action that comes out of a retrospective make them highly effective. As an added plus, retrospectives are also fun to facilitate (if you’re into that sort of thing) and generally make everyone feel more positive about the approaching sprint.

Running a retrospective is a pretty standard process but again is open for improvement and adaptation. My favored format is:

  1. What just happened? (aka “set the stage”) The team builds a brief time-line of what happened during the sprint.
  2. How are we feeling? Each team member draws a mood line of how they were feeling throughout the timeline, talking through their personal peaks and troughs during the sprint (I’d love to know how this technique came about!)
  3. Things to note! You can use whatever categories you need here, but generally Good Things, Bad Things, and Ideas work well. Some facilitators also add Bouquets─things that other team members have done during the sprint that are worthy of praise.
  4. Actions: The best way to get a short-list of actionable items is to use dot-voting/multi-voting to highlight the top three or four things that the team wants to address. If these items are related to the product they’re moved into the product backlog. If they are process related they generally become the project lead/Scrum Master’s (or sometimes Product Owner’s) responsibility.
  5. Close the retrospective: Check how the retrospective went, and confirm the next steps.

For a bigger retrospective, particularly in between project phases, I think it’s good to use a more elaborate Innovation Game to generate ideas for how things could be better next time. I like Remember the Future─it’s a game that can be used for either product brainstorming or focused towards the effectiveness of the whole team.
Retrospectives are a good habit to get into. They can also be used in non-Agile delivery as well (i.e. in Waterfall, running a retrospective after the completion of every milestone).

More on retrospectives
There are some good books (Agile Retrospectives) and many articles around the web but ultimately you need to run one, get feedback from the team and start improving. Some useful starters:

  • An action planning focused method
  • Another on product level retrospectives
  • A useful article on improving your retrospectives—you’ll get the idea soon enough.

 

3months
3months are a 16 year old, independent software services company with offices in Auckland and Wellington, New Zealand. We specialise in helping organisations of all sizes (from entrepreneurs through to large corporates, government agencies and international advertising agencies) conceive and build new generation web & mobile software solutions, fast.
3months
3months are a 16 year old, independent software services company with offices in Auckland and Wellington, New Zealand. We specialise in helping organisations of all sizes (from entrepreneurs through to large corporates, government agencies and international advertising agencies) conceive and build new generation web & mobile software solutions, fast.

The Related Post

This is part 1 of a 2-part series. The 1st part will discuss the culture and mindset around Agile, and how Agile Quadrants are used. Part 2 will discuss how to use the Agile Quadrant, the significance of Automation in Agile Quadrants and how to use Agile Quadrants to overcome Quality Assurance headaches. Organizations aspire ...
When quality assurance teams and management who have adopted Agile practices first put the ideas to work, they face a significant impediment in unlearning the traditional mind-set and practices that experience in traditional practices has instilled in them. “He who knows to unlearn, learns best.” — Anonymous The following are some of the key aspects ...
Our comprehensive issue on Agile, which was set to be released in June, has been moved to early July. We’ve made this decision in order to accommodate an article from one of our industry’s thought leaders. We’re really excited about this piece and we’re sure you will be too! LogiGear Magazine is dedicated to bringing ...
Video narrated by MICHAEL HACKETT – Certified ScrumMaster This is Part Two Continued of a Four Part Video on “New Roles for Traditional Testers in Agile Development” Michael shares his thoughts on “A Primer – New Roles for Traditional Testers in Agile” LogiGear Corporation LogiGear Corporation LogiGear Corporation provides global solutions for software testing, and ...
If your Agile implementation is not about people, you’ve missed the boat! The most profound impact to becoming more Agile is happier teams! Agile manifesto Value #1: * Individuals and interactions over processes and tools Words like these do not show up in Waterfall or RUP SDLC process descriptions. Agile cannot get more basic than ...
This article presents ten tips for Agile testing based on our experience. However, don’t expect to find the perfect test approach for your company or software project in this article. That is still something you will have to find out yourself! Several years ago I started as test manager on a J2EE project. The project ...
The No-Nonsense Guide for How to Write Smarter and Low Maintenance Test Cases Test design is a phrase that is often used when planning testing and test efforts, but I do not believe it is well understood. Also, opinions vary widely about the importance of test design ranging from irrelevant to the crucial ingredient for ...
Continuous Improvement and Short Feedback loops (think: Test Driven Development; Sprint Demo/Review; …) are at the core of any Agile process. Without a structured improvement process it can be difficult for teams to improve and without improvement we stagnate. For methods like Scrum, XP and et al., Retrospectives are that tool.
Application development and delivery teams are under constant pressure to release quality features as quickly as possible. CIOs rate delivering applications faster, with higher quality and with strong control on application development as their key priorities. What’s more, supporting this type of agile environment is particularly complex to IT teams that are also tasked with supporting ...
LogiGear Magazine July 2012 Testing in Agile  
As CTO of Xebia and highly experienced in offshore testing in India, Guido articulates his methods in addressing common challenges faced by the in-house and offshore teams. He weighs heavily on strategic tactics as well as key cultural aspects to execute efficient and effective Agile methods. 1. I work at a US-based company and we ...
Over the years many Agile proponents have come out strongly against offshoring some of the development team, and in particular against having a remote testing team. We made use of not one, but two separate outsourcing providers located in two distant locations. While we had many challenges, what we found was that by starting with ...

Leave a Reply

Your email address will not be published. Required fields are marked *

Stay in the loop with the lastest
software testing news

Subscribe