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 |  DevOps ChatOps |  Agile Start Stop Continue |  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. | For operational work in a distributed team, the method links communication with direct system control. It records decisions right where the signal, the context, and the execution come together. | When a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. | 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 | Medium | Low | Low |
Timedifferent | Halber Tag | Ongoing | 30-60 min | 45-90 min |
Participantsdifferent | 5-20 | 2-20 | 3-12 | 4-12 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Simulation Notes, Gaps List, Updated Runbooks | Chat Transcript, Action Log, Automations | Start Stop Continue Board, Improvement Actions | Sailboat Board, Risks, Improvement Actions |
Tagsno overlap | ResilienceOperationsIncident | CollaborationEngineeringIncident | RetrospectiveImprovementTeamReflection | RetrospectiveTeamImprovement |