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 | ![]() Decision Making Assumption Surfacing | ![]() Decision Making Pre-Mortem | ![]() Product Discovery Dual-Track Agile |
|---|---|---|---|---|
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. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. | 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. | When uncertainty and delivery run in parallel, it separates learning work from implementation while keeping both connected. It prevents unvalidated ideas from falling directly into the delivery stream. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 1-4 Wochen je Sprint, laufend | 45-90 min | 20–45 min | Laufend, Wochen bis Monate |
Participantsdifferent | 3-10 (Scrum Team) | 2-8 | Small cross-functional group | 4-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Assumption List, Critical Assumptions, Learning Plan | Risk list, Mitigation plan, Assumption log | Discovery Backlog, Delivery Backlog, Experiment-Ergebnisse, Validierte Stories |
Tagsno overlap | AgileIterationCadence | AssumptionsRiskDecisionDiscovery | RiskDecisionFailurePlanning | AgileDiscoveryDelivery |



