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 ATAM (Architecture Tradeoff Analysis Method) |  Architecture Architecture Decision Record |  Delivery RAID Log |
|---|---|---|---|---|
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. | ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation. | 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. |
Complexitydifferent | High | High | Low | Low |
Timedifferent | Halber Tag | Several meetings plus preparation and analysis; total effort depends on scope | 15-45 min | 30 min Setup, dann laufend |
Participantsdifferent | 5-20 | Evaluation team, architects, and relevant stakeholders | 1-3 | 1-3 maintaining, briefing for everyone |
Formatdifferent | Workshop | Workshop + async | Async | Async |
Outputdifferent | Simulation Notes, Gaps List, Updated Runbooks | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | ADR File, Decision Log, Rationale | RAID Log, Status Report Source |
Tagsno overlap | ResilienceOperationsIncident | ArchitectureQualityRiskTradeoffsStakeholders | ArchitectureRationaleDocumentationGovernance | RiskTrackingStakeholdersGovernance |