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
Decision Tree method illustration showing its working structure
Decision Making
Decision Tree
Paper illustration for Planning Poker.
Agile
Planning Poker
A hypothetical failure makes concrete risks, signals, and fitting mitigations visible.
Decision Making
Pre-Mortem
Paper illustration for Affinity Estimation.
Agile
Affinity Estimation
Purposedifferent
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 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.When many tasks need to be classified quickly, it sorts them by perceived effort and similarity. It reduces the effort of fine-grained estimation for large volumes.
Complexitydifferent
MediumLowLowMedium
Timedifferent
30-90 min2-5 min je Item20–45 min30-90 min
Participantsdifferent
1-63-9Small cross-functional group3-12
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Decision Tree, Option Map, Assumption ListRelative Estimates, Assumption Notes, Split CandidatesRisk list, Mitigation plan, Assumption logAffinity Size Map, Grouped Estimates, Unclear Items
Tagsno overlap
DecisionTreeOptions
EstimationAgileRelative sizingTeam
RiskDecisionFailurePlanning
EstimationBacklogRelative sizing
Add more methods