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 Affinity Estimation.
Agile
Affinity Estimation
Paper illustration for Planning Poker.
Agile
Planning Poker
Paper illustration for Ideal Days.
Agile
Ideal Days
Paper illustration for Dot Estimation.
Facilitation
Dot Estimation
Purposedifferent
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 estimates within the team diverge too much, it puts differing expectations on a common test bench. It separates rough complexity from unspoken assumptions.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 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.
Complexitydifferent
MediumLowLowLow
Timedifferent
30-90 min2-5 min je Item15-60 min5-20 min
Participantsdifferent
3-123-92-93-20
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Affinity Size Map, Grouped Estimates, Unclear ItemsRelative Estimates, Assumption Notes, Split CandidatesIdeal Day Estimates, Assumption Notes, Capacity CaveatsEffort Heatmap, Risk Signals, Discussion Targets
Tags1 shared
EstimationBacklogRelative sizing
EstimationAgileRelative sizingTeam
EstimationEffortAgile
EstimationEffortRisk
Add more methods