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 |  Engineering Failure Scenario Analysis |  Decision Making Constraint Analysis |  Decision Making Red Teaming |
|---|---|---|---|---|
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. | In critical processes, it is not enough to plan only for the normal case. Failure Scenario Analysis looks at the path into failure and shows which failures, chains, and control gaps cause the most damage. | When an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped. | For strategic decisions with high reach, agreement and gut feeling are often not enough. Red teaming brings deliberate opposition into the situation and tests where a plan breaks under real counterarguments. |
Complexitydifferent | Medium | Medium | Low | High |
Timedifferent | 1-4 Wochen je Sprint, laufend | 1-3 h | 30-90 min | 1-4 h |
Participantsdifferent | 3-10 (Scrum Team) | 3-8 | 2-8 | 3-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | Constraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries | Challenge Findings, Risk Register, Mitigation Plan |
Tagsno overlap | AgileIterationCadence | FailureResilienceRisk | ConstraintsDecisionPlanningOptions | RiskDecisionSensemaking |