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
Decision Tree method illustration showing its working structure
Decision Making
Decision Tree
Paper illustration for Affinity Estimation.
Agile
Affinity Estimation
Paper illustration for Ideal Days.
Agile
Ideal Days
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.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 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.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.
Complexitydifferent
LowMediumMediumLow
Timedifferent
2-5 min je Item30-90 min30-90 min15-60 min
Participantsdifferent
3-91-63-122-9
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Relative Estimates, Assumption Notes, Split CandidatesDecision Tree, Option Map, Assumption ListAffinity Size Map, Grouped Estimates, Unclear ItemsIdeal Day Estimates, Assumption Notes, Capacity Caveats
Tagsno overlap
EstimationAgileRelative sizingTeam
DecisionTreeOptions
EstimationBacklogRelative sizing
EstimationEffortAgile
Add more methods