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 Sprint 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 is over and friction shouldn't simply be carried forward, it opens the view onto collaboration and patterns. It creates space to see causes and changes together. | 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 | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 20-45 min |
Participantsdifferent | 5-20 | 4-12 | Scrum Team | 3-12 |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Simulation Notes, Gaps List, Updated Runbooks | Starfish Board, Practice Changes, Experiments | Improvement actions, Team agreements | Lessons learned, Action items, Event summary |
Tagsno overlap | ResilienceOperationsIncident | RetrospectiveImprovementExperimentsTeam | RetrospectiveImprovementLearning | LearningOperationsImprovement |