methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration of Scrum with its method-specific working model.
Agile
Scrum
Red Teaming method illustration showing its working structure
Decision Making
Red Teaming
Paper illustration for Argument Mapping
Decision Making
Argument Mapping
A hypothetical failure makes concrete risks, signals, and fitting mitigations visible.
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.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 statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on.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
MediumHighMediumLow
Timedifferent
1-4 Wochen je Sprint, laufend1-4 h1-3 h20–45 min
Participantsdifferent
3-10 (Scrum Team)3-81-8Small cross-functional group
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
Product Backlog, Sprint Backlog, Increment, Sprint GoalChallenge Findings, Risk Register, Mitigation PlanArgument Map, Evidence Gaps, Decision RationaleRisk list, Mitigation plan, Assumption log
Tagsno overlap
AgileIterationCadence
RiskDecisionSensemaking
SensemakingDecisionRationale
RiskDecisionFailurePlanning
Add more methods