iterate-retrospective

1<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
2# Retrospective
3 
4A retrospective is a structured reflection that helps teams learn from their experiences and continuously improve. By regularly examining what went well, what didn't, and what to change, teams build a culture of learning and adaptation. The value isn't just in the discussion.it's in the documented actions and follow-through.
5 
6## When to Use
7 
8- At the end of every sprint (for agile teams)
9- After completing a significant project or milestone
10- Following a major incident or outage
11- When team dynamics feel off and need addressing
12- At regular intervals (monthly, quarterly) even without specific triggers
13- When onboarding new team members to establish improvement culture
14 
15## When NOT to Use
16 
17- You want one durable learning banked for the organization -> use `iterate-lessons-log`; the retro is the ceremony, the log entry outlives it
18- You are scoring an OKR cycle at close -> use `measure-okr-grader`
19- The reflection must end in a pivot-or-persevere call -> use `iterate-pivot-decision`
20- You need a recap of a general (non-retro) meeting -> use `foundation-meeting-recap`
21 
22## Instructions
23 
24When asked to facilitate or document a retrospective, follow these steps:
25 
261. **Set the Context**
27   Define what period or project this retrospective covers, who attended, and any significant events that occurred. This frames the discussion and helps future readers understand the context.
28…