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 |  Decision Making Pre-Mortem |  Architecture arc42 |  Architecture Architecture Decision Record |
|---|---|---|---|---|
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 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. | 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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. |
Complexitydifferent | High | Low | Low | Low |
Timedifferent | 90-180 min | 20–45 min | 1-2 Tage | 15-45 min |
Participantsdifferent | 3-8 | Small cross-functional group | 1-4 | 1-3 |
Formatdifferent | Workshop | Workshop | Workshop + async | Async |
Outputdifferent | CoD Table, Prioritization Sequence | Risk list, Mitigation plan, Assumption log | Architecture Document, Context View, Runtime View, Deployment View | ADR File, Decision Log, Rationale |
Tagsno overlap | PrioritizationDeliveryEconomicsDecision | RiskDecisionFailurePlanning | ArchitectureDocumentationCommunication | ArchitectureRationaleDocumentationGovernance |