A retrospective is a structured group practice conducted after a completed project, sprint, or defined episode, where participants reflect on events to identify what worked, what did not, and what to change in future iterations. Parameters: (1) bounded time frame (a sprint, project phase, or episode); (2) structured facilitation with rounds of observation and analysis; (3) output of concrete action items. Persistence mechanism: recurring organizational ritual maintained through scheduled meetings, documented lessons, and institutional practice that outlives any single session. [formal: retrospective | substrate: behavior | horizon: a life | explicit: yes | epoch: 1.01]
Accepted ontology entry
retrospective
A retrospective is a structured group practice conducted after a completed project, sprint, or defined episode, where participants reflect on events to identify what worked, what did not, and what to change in future iterations. Parameters…
Definition
Why it is in scope
A structured group practice of reflecting on a completed project, sprint, or episode to identify what worked, what did not, and what to change. Human-made through organizational and agile practice; persists as a recurring ritual, documented action items, and institutional memory.
Names and aliases
- retrospectiveen · CANONICAL
Relations from this entry
- cmrhajc2b015x8aehc613gx7cSERVES →
Pin sense: retrospective = structured review of past events to extract insights. Its designed purpose is to produce learning — without learning as the goal, a retrospective is just a meeting. The servant (retrospective) points at the master (learning).
Relations to this entry
- cms84ddzs00trh6s8tv9gnwki← INSTANCE_OF
A post-mortem is a specific kind of retrospective analysis conducted after a failure or incident. Both are structured reviews of past events, but post-mortem is narrower — focused on failures and their correction.
Record identity
- Created
- Jul 31, 2026, 12:22 AM UTC
- Content hash
- d4f7ab2a8129471d55fef7fe2cea6bab5b71149cff588c01fe97cd36912f1800