Notice: We are aware that many of the Chewiki’s images are still broken. We promise: we will try our best to fix it, but we don't guarantee that the fix will be trivial.
What Is An Agile Retrospective
An Agile retrospective is a gathering that is held at the finish of an iteration in Agile software development. Throughout the retrospective, the workforce reflects on what occurred in the iteration and identifies actions for improvement going forward.
Each member of the workforce 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 Online Retrospective Tools may be thought of as a "lessons learned" meeting. The staff reflects on how everything went and then decides what adjustments they want to make within the next iteration. The retrospective is crew-driven, and crew members should resolve together how the meetings will be run and the way decisions will be made about improvements.
Because Agile stresses the importance of continuous improvement, having a daily Agile retrospective is one of the most important of Agile development practices. The Ninth Agile principle outlined in the Agile manifesto states, "At regular intervals, the workforce reflects on tips on how to turn out to be more effective, then tunes and adjusts its habits accordingly." A framework, such as the one beneath, can be used to provide structure and keep discussion during the retrospective focused.
Set the stage - get the crew ready to engage within the retrospective, maybe with a warm-up activity such as Plus, Minus, Fascinating (PMI) (5 minutes).
Collect data - create a shared picture of what occurred in the course of the retrospective (10 minutes).
Generate insights - focus on what was profitable and identify any roadblocks to success (10 minutes).
Determine what to do - determine highest priority items to work on and put measurable goals on those items so they can be completed (quarter-hour).
Shut the retrospective - mirror on the retrospective and the way to improve it, and to appreciate accomplishments of the staff and particular person interactions (5 minutes).
The form above is just not the only way to hold an Agile retrospective. You will need to consider other alternate options which embrace, however should not limited to project publish mortems, PMI retrospectives, six hats retrospectives, and asking the five whys.
