What are they?
Retrospectives provide opportunities for groups to reflect, inspect and adapt their ways of working. They often take place at the end of sprints but can be scheduled at any time.
Why use Retrospectives?
Retrospectives facilitate continuous improvement. Rather than wait until the end of a project to run a full “lessons learned” exercise for the entire delivery, we encourage taking short time boxes during delivery for the team to course correct and find ways to improve their way of working. This should come in the form of actions agreed by the team with owners and estimated time due dates, allowing for tracking and helping to ensure their completion.
Many practices benefit from their artefacts being re-visited, reflected upon and/or updated during retrospectives including:
Engineering practices such as Continuous Integration and Test Automation can also benefit from being considered during retrospectives. In particular, exporting data from associated tools to give teams the opportunity for the team to review the data, inspect trends and establish whether any adaption in behaviour or practice would enable them and measurements to improve.
The Realtime-Retrospective is a very similar practice which runs continuously and captured feedback in real time.
Who do you need?
- The Team
- Varies based on the duration of the time period the retrospective is covering. We recommend allowing 30-60 minutes for a one week sprint retrospective.
- Facilitator: Easy
- Participants: Easy
Facilitation Materials Needed
There are lots of different formats retrospectives can take (see the references for links to some excellent resources which provide ideas). Typical materials used during facilitation include:
- Flat space which will hold sticky notes
- Stickies (preferably a wide variety)
- Sharpie pens
- White-board pens if using a white board or MagicWhiteboard paper
- Clock for time boxing
How does it fit?
- Typically done in the Learn and Measure area of the Delivery of the Open Practice Library
- Be careful not to dwell too heavily on things outside of the teams control. Ensure you track them and raise them to the relevant owners but value can rarely be found in a one hour ranting session.
- Retro’s are within reason whatever a team needs to be. They can be broad and encompass multiple issues and problems, or with the teams permission can drill down into specific issues using techniques such as the 5 whys.
- Locations can play a major role in the outcome of a Retrospective. Changing a Retro location to a Cafe, pub or even using techniques such as the walking retro can help to drive out different problems/issues that might not have come up otherwise