...
During each Agile Retrospective, the Agile Team plans ways to increase product quality by improving work processes or adapting the definition of “Done” if appropriate and not in conflict with product or organisational standards - according to http://scrum.org . The outputs of a Agile Retrospective are those identified improvements by the Development Team, which could be implemented in the next development periods.
What does a typical Agile Retrospective look like?
(According to Esther Derby and Diana Larsen (Agile Retrospectives – Making Good teams great. External source: https://pragprog.com/titles/dlret/agile-retrospectives/ )
...
Set the stage
Set the goal
Give people time to “arrive” and get into the right mood
...
Gather data
Help everyone remember
Create a shared pool of information (everybody sees the world differently)
...
Generate insight
Why did things happen the way they did?
Identify patterns
See the big picture
...
Decide what to do
Pick a few issues to work on and create concrete action plans of how you’ll address them
Close the retrospective
...
Clarify follow-up
...
Appreciations
...
Clear end
...
period.