View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Game DayFailure Mode and Effects AnalysisRisk StormingLASR (Lightweight Approach for Software Reviews)
| Criterion |  DevOps Game Day |  Operations Failure Mode and Effects Analysis |  Architecture Risk Storming |  Architecture LASR (Lightweight Approach for Software Reviews) |
|---|---|---|---|---|
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 a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability. | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. | LASR helps development teams identify where their software falls short of important quality goals and which improvements to consider. A small group with existing system knowledge can make an initial assessment and investigate open questions in more detail. |
Complexitydifferent | High | High | Low | Medium |
Timedifferent | Halber Tag | 2-6 h | 60-90 min | 3–4 h for initial assessment; preparation and deeper analysis additional |
Participantsdifferent | 5-20 | 3-10 | 4-12 | 1 or a small team; particularly suitable for 3–4 people |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Simulation Notes, Gaps List, Updated Runbooks | FMEA Table, Risk Priority, Mitigation Actions | Annotated Diagram, Prioritized Risk List, Action Backlog | Lean Mission Statement describing the software’s purpose, Prioritized quality goals and evaluation criteria, Risks and estimated gaps against quality goals, More closely examined findings and open checks |
Tagsno overlap | ResilienceOperationsIncident | RiskQualityOperationsRoot cause | RiskArchitectureWorkshopValidation | ArchitectureQualityRiskAssessmentLean |