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 |  Delivery RAID Log |  Decision Making Pre-Mortem |
|---|---|---|---|
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. | 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. | 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 | Medium | Low | Low |
Timedifferent | 1-4 Wochen je Sprint, laufend | 30 min Setup, dann laufend | 20–45 min |
Participantsdifferent | 3-10 (Scrum Team) | 1-3 maintaining, briefing for everyone | Small cross-functional group |
Formatdifferent | Workshop + async | Async | Workshop |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | RAID Log, Status Report Source | Risk list, Mitigation plan, Assumption log |
Tagsno overlap | AgileIterationCadence | RiskTrackingStakeholdersGovernance | RiskDecisionFailurePlanning |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
