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 Sailboat Retrospective |  Operations Learning Review |  Agile Starfish Retrospective |
|---|---|---|---|---|
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 a team wants to read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture. | 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. | 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. |
Complexitydifferent | High | Low | Medium | Low |
Timedifferent | Halber Tag | 45-90 min | 1-3 h | 45-90 min |
Participantsdifferent | 5-20 | 4-12 | 3-10 | 4-12 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Simulation Notes, Gaps List, Updated Runbooks | Sailboat Board, Risks, Improvement Actions | Learning Review Notes, System Factors, Improvement Actions | Starfish Board, Practice Changes, Experiments |
Tagsno overlap | ResilienceOperationsIncident | RetrospectiveTeamImprovement | LearningRetrospectiveIncidentOperations | RetrospectiveImprovementExperimentsTeam |