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 for Planning Poker.
Agile
Planning Poker
A hypothetical failure makes concrete risks, signals, and fitting mitigations visible.
Decision Making
Pre-Mortem
Decision Tree method illustration showing its working structure
Decision Making
Decision Tree
Paper illustration for Constraint Analysis.
Decision Making
Constraint Analysis
Purposedifferent
When estimates within the team diverge too much, it puts differing expectations on a common test bench. It separates rough complexity from unspoken assumptions.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.For decisions with follow-on paths and dependencies, a linear comparison is often not enough. A Decision Tree shows how options branch under conditions and which consequences hang on each branch.When an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped.
Complexitydifferent
LowLowMediumLow
Timedifferent
2-5 min je Item20–45 min30-90 min30-90 min
Participantsdifferent
3-9Small cross-functional group1-62-8
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Relative Estimates, Assumption Notes, Split CandidatesRisk list, Mitigation plan, Assumption logDecision Tree, Option Map, Assumption ListConstraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries
Tagsno overlap
EstimationAgileRelative sizingTeam
RiskDecisionFailurePlanning
DecisionTreeOptions
ConstraintsDecisionPlanningOptions
Add more methods