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 4Ls Retrospective |  Agile Sailboat 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 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. | 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. |
Complexitydifferent | High | Low | Low |
Timedifferent | Halber Tag | 45–75 min | 45-90 min |
Participantsdifferent | 5-20 | Team members involved | 4-12 |
Formatsame | Workshop | Workshop | Workshop |
Outputdifferent | Simulation Notes, Gaps List, Updated Runbooks | 4Ls Board, Learning Themes, Improvement Actions | Sailboat Board, Risks, Improvement Actions |
Tagsno overlap | ResilienceOperationsIncident | RetrospectiveLearningReflectionTeam | RetrospectiveTeamImprovement |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
