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 Sprint 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 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. |
Complexitydifferent | High | Low | Medium | Low |
Timedifferent | Halber Tag | 45-90 min | 1-3 h | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter |
Participantsdifferent | 5-20 | 4-12 | 3-10 | Scrum Team |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Simulation Notes, Gaps List, Updated Runbooks | Sailboat Board, Risks, Improvement Actions | Learning Review Notes, System Factors, Improvement Actions | Improvement actions, Team agreements |
Tagsno overlap | ResilienceOperationsIncident | RetrospectiveTeamImprovement | LearningRetrospectiveIncidentOperations | RetrospectiveImprovementLearning |