What is a retrospective?
This is an abstract.
In the agile context, a retrospective is an - often regular - team meeting held with the goal of looking back at the most recent collaboration. This is analyzed and measures are derived with the aim of continuously improving the way of working.
The purpose of the retrospective is to plan and discuss ways to increase effectiveness and quality. The team reviews the last few weeks of collaboration in terms of individuals, processes, and tools. The team discusses different topics during a retrospective: what went well?, what problems have we encountered, how did we as a team solve these problems (or what is still missing to a solution)?.
In many agile frameworks, retrospectives have a regular place and are conducted at a regular pace. In Scrum, for example, the retrospective is part of the Scrum events and takes place once per sprint cycle (i.e. at least once a month). With the retrospective view on joint collaboration and the problems that arise, the teams attempt to identify the recognized impediments at an early stage and to address them directly: As opposed to just a single "lessons learned session" after a project is completed.
What are the characteristics of good retrospectives?
The retrospective takes place regularly.
The benefit of this event for a team comes from its regularity and the current reference to the past collaboration.