Hold the Iteration Retrospective

Objective

Convert the iteration's delivery and assessment evidence into owned learning without rewriting history.

Required inputs

• Iteration Frame and accepted PIN/MIN records.
• Release/acceptance evidence.
• Latest complete Iteration Assessment Report and Project-Management Tickets.
• Charter and participants named in its Team Roster.

Procedure

1. Create docs/project/retros/<iteration_id>.md.
2. Compare planned versus actual outcome, duration, throughput, quality, coordination, and assessment signals.
3. For each material variance, record evidence, causal hypothesis, impact, and whether it is:
   - a product/code/delivery concern to track as backlog or Risk/Problem ticket; or
   - a repeatable process concern eligible for an IIP.
4. Record decisions, action owners, due dates, and experiments. Do not turn every complaint into a process change.
5. Reassess team maturity only when the iteration produced relevant evidence; update the Charter with evidence and date, not intuition.

Completion evidence

The retrospective cites source records, separates fact from interpretation, classifies each concern, assigns every accepted action, records unchanged/open questions, and has participant acknowledgment.