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 |  Architecture Architecture Decision Record |  Delivery RAID Log |  Architecture Views and Beyond |
|---|---|---|---|---|
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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question. |
Complexitydifferent | High | Low | Low | Medium |
Timedifferent | Halber Tag | 15-45 min | 30 min Setup, dann laufend | 1-3 Tage |
Participantsdifferent | 5-20 | 1-3 | 1-3 maintaining, briefing for everyone | 1-4 |
Formatdifferent | Workshop | Async | Async | Workshop + async |
Outputdifferent | Simulation Notes, Gaps List, Updated Runbooks | ADR File, Decision Log, Rationale | RAID Log, Status Report Source | Architecture Views, Cross-view Notes, Rationale |
Tagsno overlap | ResilienceOperationsIncident | ArchitectureRationaleDocumentationGovernance | RiskTrackingStakeholdersGovernance | DocumentationStakeholdersArchitecture |