An Agile retrospective is a meeting that is held on the end of an iteration in Agile software development. Through the retrospective, the workforce reflects on what happened within the iteration and identifies actions for improvement going forward.
Every member of the team members solutions the following questions:
What worked well for us?
What didn’t work well for us?
What actions can we take to improve our process going forward?
The Agile retrospective could be thought of as a «lessons learned» meeting. The group reflects on how everything went after which decides what adjustments they want to make in the next iteration. The retrospective is staff-driven, and workforce members should resolve together how the conferences will be run and how decisions will be made about improvements.
Because Agile stresses the significance of continuous improvement, having an everyday Agile retrospective is likely one of the most important of Agile development practices. The Ninth Agile precept outlined within the Agile manifesto states, «At regular intervals, the crew reflects on how one can become more effective, then tunes and adjusts its conduct accordingly.» A framework, such because the one below, can be used to provide structure and keep discussion in the course of the retrospective focused.
Set the stage — get the group ready to have interaction in the retrospective, maybe with a warm-up activity equivalent to Plus, Minus, Interesting (PMI) (5 minutes).
Gather data — create a shared picture of what happened through the retrospective (10 minutes).
Generate insights — focus on what was profitable and establish any roadblocks to success (10 minutes).
Determine what to do — identify highest priority items to work on and put measurable goals on those items to allow them to be completed (quarter-hour).
Close the retrospective — reflect on the retrospective and tips on how to improve it, and to appreciate accomplishments of the workforce and individual interactions (5 minutes).
The form above will not be the only way to hold an Agile retrospective. You will need to consider other alternate options which embody, but aren’t limited to project publish mortems, PMI retrospectives, six hats retrospectives, and asking the five whys.
Here is more on Online Retrospective take a look at our own website.