Introduction
This skill helps a team identify practices worth keeping and changes worth making from a real period of work. It selects a retrospective format suited to the group, gathers facts and feelings, identifies patterns and causes, and converts discussion into a small set of actions with owners, deadlines, and verification. Different views of disputed events remain visible to prevent premature attribution.
Use Cases
Use it after a sprint, project phase, incident, campaign, or quarter. It focuses on process and systems rather than blame and checks previous actions so each session does not merely produce another wish list.
Template
Provide the scope, timeline, goal, outcome, important events, data, participants, and sensitive areas. The output includes an agenda, prompts, factual summary, patterns, causes, practices to keep, improvements, and trackable actions.
