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 Mad Sad Glad |  Agile Starfish 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 team's or workshop's mood needs to become readable, it structures emotional signals with little setup. It makes strain, relief, and sources of energy tangible. | 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 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 | Low |
Timedifferent | Halber Tag | 30-60 min | 45-90 min | 45-90 min |
Participantsdifferent | 5-20 | 3-10 | 4-12 | 4-12 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Simulation Notes, Gaps List, Updated Runbooks | Emotion Board, Themes, Action Items | Starfish Board, Practice Changes, Experiments | Sailboat Board, Risks, Improvement Actions |
Tagsno overlap | ResilienceOperationsIncident | RetrospectiveTeamReflection | RetrospectiveImprovementExperimentsTeam | RetrospectiveTeamImprovement |