View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Delivery Cost of Delay |  Engineering Failure Scenario Analysis |  Architecture arc42 |  Decision Making Pre-Mortem |
|---|---|---|---|---|
Purposedifferent | Helps clarify scope, order, and delivery flow in concrete terms. It makes work, constraints, and sequence manageable. The result is captured as a Cost of Delay table and prioritization sequence. | 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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | In early initiatives with many uncertainties, planning quickly turns too optimistic. A pre-mortem makes the expected failure visible in advance and sharpens the view of causes, gaps, and countermeasures. |
Complexitydifferent | High | Medium | Low | Low |
Timedifferent | 90-180 min | 1-3 h | 1-2 Tage | 20–45 min |
Participantsdifferent | 3-8 | 3-8 | 1-4 | Small cross-functional group |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | CoD Table, Prioritization Sequence | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | Architecture Document, Context View, Runtime View, Deployment View | Risk list, Mitigation plan, Assumption log |
Tagsno overlap | PrioritizationDeliveryEconomicsDecision | FailureResilienceRisk | ArchitectureDocumentationCommunication | RiskDecisionFailurePlanning |