View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile Scrum |  Operations Fault Tree Analysis |  Delivery RAID Log |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|---|
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. | For a critical top event with several possible triggers, the method logically models failure paths. It makes visible which combinations of conditions can lead to damage. | 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. | 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. |
Complexitydifferent | Medium | High | Low | High |
Timedifferent | 1-4 Wochen je Sprint, laufend | 2-6 h | 30 min Setup, dann laufend | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 3-10 (Scrum Team) | 3-8 | 1-3 maintaining, briefing for everyone | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + async |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Fault Tree, Critical Paths, Cause Hypotheses, Control Actions | RAID Log, Status Report Source | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations |
Tagsno overlap | AgileIterationCadence | RiskRoot causeSafety | RiskTrackingStakeholdersGovernance | ArchitectureQualityRiskTradeoffsStakeholders |