View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:ScrumArchitecture Decision RecordFailure Mode and Effects AnalysisLASR (Lightweight Approach for Software Reviews)
| Criterion |  Agile Scrum |  Architecture Architecture Decision Record |  Operations Failure Mode and Effects Analysis |  Architecture LASR (Lightweight Approach for Software Reviews) |
|---|---|---|---|---|
Purposedifferent | When a team needs to work in a fixed delivery rhythm, it stabilizes cadence, responsibility, and feedback loops. It makes collaboration reliable across sprint boundaries. | 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. | 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. | 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 | Medium | Low | High | Medium |
Timedifferent | 1-4 Wochen je Sprint, laufend | 15-45 min | 2-6 h | 3–4 h for initial assessment; preparation and deeper analysis additional |
Participantsdifferent | 3-10 (Scrum Team) | 1-3 | 3-10 | 1 or a small team; particularly suitable for 3–4 people |
Formatdifferent | Workshop + async | Async | Workshop | Workshop + async |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | ADR File, Decision Log, Rationale | FMEA Table, Risk Priority, Mitigation Actions | 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 | AgileIterationCadence | ArchitectureRationaleDocumentationGovernance | RiskQualityOperationsRoot cause | ArchitectureQualityRiskAssessmentLean |