View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  DevOps Game Day |  Agile Starfish Retrospective |  Agile 4Ls Retrospective |  Operations After-Action Review |
|---|---|---|---|---|
Purposedifferent | In preparing for rare incidents, the method tests response capability under controlled conditions. It shows where assumptions about stability, roles, and recovery are too optimistic. | When improvement options need to be sorted more finely than just start and stop, it brings observations into clear kinds of action. This makes visible what should be done more, less, newly, or continued. | When a sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time. | After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement. |
Complexitydifferent | High | Low | Low | Low |
Timedifferent | Halber Tag | 45-90 min | 45–75 min | 20-45 min |
Participantsdifferent | 5-20 | 4-12 | Team members involved | 3-12 |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Simulation Notes, Gaps List, Updated Runbooks | Starfish Board, Practice Changes, Experiments | 4Ls Board, Learning Themes, Improvement Actions | Lessons learned, Action items, Event summary |
Tagsno overlap | ResilienceOperationsIncident | RetrospectiveImprovementExperimentsTeam | RetrospectiveLearningReflectionTeam | LearningOperationsImprovement |