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 Red Teaming |  Decision Making Cynefin Workshop |
|---|---|---|---|---|
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. | 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. | When problems are unclear, chaotic, or only seemingly familiar, standard recipes fall short. A Cynefin Workshop sorts situations by the nature of their problem and connects them with matching action logic. |
Complexitydifferent | Medium | Medium | High | Medium |
Timedifferent | 1-4 Wochen je Sprint, laufend | 1-3 h | 1-4 h | 60-180 min |
Participantsdifferent | 3-10 (Scrum Team) | 3-8 | 3-8 | 4-20 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | Challenge Findings, Risk Register, Mitigation Plan | Cynefin Map, Domain-specific Actions, Sensemaking Notes |
Tagsno overlap | AgileIterationCadence | FailureResilienceRisk | RiskDecisionSensemaking | ComplexitySensemakingDecision |