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 Bucket System.
Agile
Bucket System
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 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.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 ListBucketed Backlog, Relative Estimates, Split CandidatesIdeal Day Estimates, Assumption Notes, Capacity Caveats
Tagsno overlap
EstimationAgileRelative sizingTeam
DecisionTreeOptions
EstimationBacklogRelative sizing
EstimationEffortAgile
Add more methods