Project retrospective lessons

Purpose

Extracts reusable lessons from a completed project by comparing planned and actual scope, dates, cost, quality, incidents, risks, and delivery outcomes, then turns evidence into specific practice changes.

Scope

Work only on the named source records and the deliverable fields described here. Preserve source wording, identifiers, dates, amounts, statuses, and citations. Excluded: contacting people, changing source systems, making approvals, or presenting a conclusion as a completed business action. The unit of analysis is a completed project event linked to an outcome and a reusable change in practice.

Data basis

• The process-specific documents, spreadsheets, and record tables in the skill scope.
• The company policy, rubric, control matrix, template, or prior-period output named by this process.
• Run-specific period, audience, project, or decision brief when supplied.
• The unit of analysis is a completed project event linked to an outcome and a reusable change in practice.

Result

Evidence-backed lessons with impact, cause, and proposed practice. Project retrospective {date}

Quality criteria

• Every material fact and finding cites its document section, page, timestamp, table row, or record ID.
• Counts, amounts, dates, and statuses reconcile to the named source population.
• Rule outcomes show the rule and preserve source values beside normalized values.
• Missing, conflicting, excluded, and estimated items have explicit statuses.
• The written result and structured output use the same row-level findings.
• The unit of analysis is a completed project event linked to an outcome and a reusable change in practice.

Instructions

A lesson is reusable only when an observed project event, its impact, and a changed practice are all linked in the evidence.

Adapt before use

Name the project phase, affected artifact, and observed consequence for each lesson; broad statements such as “communicate better” are not accepted as deliverables. Separate preventable process causes from external events and from outcome descriptions. Each proposed practice change needs an observed trigger, expected benefit, adoption signal, and named review point when those are available.

• Add the company policy, rubric, control matrix, or approved format named in the Data basis.
• Map source column names, identifiers, status values, and date or currency conventions.
• Define the process threshold, escalation vocabulary, responsible review role, and retention rule.