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 Dot Estimation.
Facilitation
Dot Estimation
Paper illustration for Ideal Days.
Agile
Ideal Days
Paper illustration for Planning Poker.
Agile
Planning Poker
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 size or effort can only be estimated roughly, Dot Estimation condenses the group's experience into a quick range. It turns individual contributions into a visible selection. The result is captured as an Effort Heatmap, Risk Signals, and Discussion Targets.When effort needs to be thought of as real working time, it offers a simple common denominator for comparison. It sorts work by value, risk, and delivery ability. The result is captured as Ideal Day Estimates, Assumption Notes, and Capacity Caveats.When estimates within the team diverge too much, it puts differing expectations on a common test bench. It separates rough complexity from unspoken assumptions.
Complexitydifferent
MediumLowLowLow
Timedifferent
30-90 min5-20 min15-60 min2-5 min je Item
Participantsdifferent
1-63-202-93-9
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Decision Tree, Option Map, Assumption ListEffort Heatmap, Risk Signals, Discussion TargetsIdeal Day Estimates, Assumption Notes, Capacity CaveatsRelative Estimates, Assumption Notes, Split Candidates
Tagsno overlap
DecisionTreeOptions
EstimationEffortRisk
EstimationEffortAgile
EstimationAgileRelative sizingTeam
Add more methods