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 |  Operations Barrier Analysis |
|---|---|---|---|---|
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. | For a risk that can only be managed through multiple layers of protection, the method examines the effectiveness of each barrier. It shows where safeguards are missing, too weak, or fail under real conditions. |
Complexitydifferent | Medium | High | Low | Medium |
Timedifferent | 1-4 Wochen je Sprint, laufend | 2-6 h | 30 min Setup, dann laufend | 2-4 h |
Participantsdifferent | 3-10 (Scrum Team) | 3-8 | 1-3 maintaining, briefing for everyone | 2-6 |
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 | Barrier Inventory, Failure Analysis per Barrier, Action Backlog |
Tagsno overlap | AgileIterationCadence | RiskRoot causeSafety | RiskTrackingStakeholdersGovernance | Root causeSafetyIncident |