A retrospective is a regular meeting where the team looks at how it worked, not what it built, and agrees one or two things to change.
Written as practical advice. Where a step rests on established research practice, the source is listed under References. Nothing here is a universal rule.
It is about the process, not people. What is said stays in the room unless agreed otherwise.
Did they happen? If not, why not? Skipping this teaches everyone that actions do not matter.
Written alone first, then shared. It is not politeness: it tells you what to keep.
Written alone first. Group similar notes and vote on which to discuss.
Specific, with an owner and a date. Two that happen beat ten that do not.
Senior designer note“A retrospective that changes nothing teaches the team to stop being honest in them.”
Reference