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
Decision Tree method illustration showing its working structure
Decision Making
Decision Tree
Paper illustration for Planning Poker.
Agile
Planning Poker
Paper illustration for Bucket System.
Agile
Bucket System
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.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.When a large batch of work needs a fast, rough estimate, it sorts items into predefined size buckets. It sorts work by value, risk, and delivery ability. The result is captured as a Bucketed Backlog, Relative Estimates, and Split Candidates.
Complexitydifferent
LowMediumLowMedium
Timedifferent
5-20 min30-90 min2-5 min je Item30-90 min
Participantsdifferent
3-201-63-93-12
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Effort Heatmap, Risk Signals, Discussion TargetsDecision Tree, Option Map, Assumption ListRelative Estimates, Assumption Notes, Split CandidatesBucketed Backlog, Relative Estimates, Split Candidates
Tagsno overlap
EstimationEffortRisk
DecisionTreeOptions
EstimationAgileRelative sizingTeam
EstimationBacklogRelative sizing
Add more methods