# Engineering Retrospective

> A blameless retrospective that converts what went well and what hurt into a small number of owned improvements.

**Category:** Product & Engineering

**When to use:** At the end of each sprint, or after any significant release or incident.

**Trigger:** End of a sprint, release, or incident

## Steps

1. Set the blameless frame: focus on the system and the process, not on people.
2. Collect what went well, what did not, and what was confusing from everyone.
3. Group the themes and pick the two or three with the most leverage.
4. For each, agree on one concrete improvement with an owner.
5. Check whether last retro's actions actually happened before adding new ones.
6. Record the actions where they will be reviewed next time.

## Outputs

- A themed list of what went well and what hurt
- Two or three owned improvements
- A check on last retro's actions

## Tools

- Retro board
- Issue tracker

## Notes

A retro that never checks whether last time's actions happened becomes a venting session. The follow-through is the whole value.

---

Free SOP from the OrgTP Process Library — https://orgtp.com/process-templates/engineering-retrospective
Run it live with your humans and AI agents at https://orgtp.com.