Retrospectives are generally monthly or quarterly meetings that allow the team to reflect on how the product has moved along, and how the collaboration has been. A retrospective may also be held every time a feature is launched or a milestone is achieved.
The goal of the retrospective is to learn and do better, not blame and find fault. It is a safe space with no hierarchy.
Facilitation. Appoint a facilitator who is ideally a neutral third party to run the retrospective. The facilitator explains what the retrospective is for (a specific milestone or timeframe), and explains the process. During the retrospective, this person also ensures that everyone has the chance to voice their opinion, keeps discussions on track, and enforces time.
At the start of every retrospective, the facilitator reads the Prime Directive out loud.
Prime directive: Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand.
Tools. There's no replacing stickies and markers for in-person retrospectives. We have found Trello and Ideaboardz useful for online retrospectives.
Stages. There are 2 broad categories to be discussed.
Steps. These need to be repeated for each stage.
Notes.