The purpose of the iteration retrospective is to:
A.
Report progress of the work effort, what work will be done next, and review impediments
to progress.
B.
Prioritize the Product Backlog, generate development and testing estimates, and plan the
next iteration.
C.
Provide a demonstration of the features developed during the iteration, get feedback from
users, and begin testing.
D.
Identify what worked well, what did not work well, and what actions should be taken to
improve the process.
The term “retrospective” ones such as “debriefing” or “post-mortem”, for its more positive connotations.
This is also known as the “sprint retrospective”, or “iteration retrospective”, often abbreviated, e.g. “sprint retro”.
The term “reflection workshop” from Alistair Cockburn is encountered less often, though it appears to have influenced the Agile Manifesto’s wording of the corresponding principle
0
0