Registered: 6 months, 1 week ago
What is an Agile retrospective?
An Agile retrospective is a gathering that is held at the finish of an iteration in Agile software development. During the retrospective, the workforce reflects on what occurred in the iteration and identifies actions for improvement going forward.
Each member of the crew members solutions the next questions:
What worked well for us?
What did not work well for us?
What actions can we take to improve our process going forward?
The Agile retrospective might be thought of as a "lessons learned" meeting. The crew displays on how everything went and then decides what changes they wish to make in the subsequent iteration. The retrospective is workforce-pushed, and workforce members should determine collectively how the meetings will be run and the way selections will be made about improvements.
Because Agile stresses the significance of continuous improvement, having a regular Agile retrospective is one of the most essential of Agile development practices. The Ninth Agile precept outlined within the Agile manifesto states, "At common intervals, the crew reflects on how one can turn into more efficient, then tunes and adjusts its habits accordingly." A framework, such because the one beneath, can be utilized to provide construction and keep dialogue 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 reminiscent of Plus, Minus, Interesting (PMI) (5 minutes).
Gather data - create a shared picture of what occurred in the course of the retrospective (10 minutes).
Generate insights - talk about what was profitable and determine any roadblocks to success (10 minutes).
Determine what to do - identify highest priority items to work on and put measurable goals on those items so they can be completed (quarter-hour).
Close the retrospective - mirror on the retrospective and the right way to improve it, and to understand accomplishments of the staff 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 options which embody, however usually are not limited to project post mortems, PMI retrospectives, six hats retrospectives, and asking the 5 whys.
If you cherished this posting and you would like to obtain far more info regarding Online Retrospective Tools kindly stop by the web page.
Topics Started: 0
Replies Created: 0
Forum Role: Participant