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 Dot Estimation.
Facilitation
Dot Estimation
Paper illustration for Planning Poker.
Agile
Planning Poker
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Paper illustration for Ideal Days.
Agile
Ideal Days
Purposedifferent
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 estimates within the team diverge too much, it puts differing expectations on a common test bench. It separates rough complexity from unspoken assumptions.When two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects.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
LowLowHighLow
Timedifferent
5-20 min2-5 min je Item1-4 Wochen15-60 min
Participantsdifferent
3-203-91-62-9
Formatdifferent
WorkshopWorkshop + asyncAsyncWorkshop + async
Outputdifferent
Effort Heatmap, Risk Signals, Discussion TargetsRelative Estimates, Assumption Notes, Split CandidatesExperiment results, Decision log, Learning summaryIdeal Day Estimates, Assumption Notes, Capacity Caveats
Tagsno overlap
EstimationEffortRisk
EstimationAgileRelative sizingTeam
ExperimentsGrowthAnalyticsValidation
EstimationEffortAgile
Add more methods