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 Learning 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 a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights. |
Complexitydifferent | High | Low | Low | Medium |
Timedifferent | Halber Tag | 45-90 min | 45–75 min | 1-3 h |
Participantsdifferent | 5-20 | 4-12 | Team members involved | 3-10 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Simulation Notes, Gaps List, Updated Runbooks | Starfish Board, Practice Changes, Experiments | 4Ls Board, Learning Themes, Improvement Actions | Learning Review Notes, System Factors, Improvement Actions |
Tagsno overlap | ResilienceOperationsIncident | RetrospectiveImprovementExperimentsTeam | RetrospectiveLearningReflectionTeam | LearningRetrospectiveIncidentOperations |