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
Decision Tree method illustration showing its working structure
Decision Making
Decision Tree
Paper illustration for Planning Poker.
Agile
Planning Poker
Paper illustration for Ideal Days.
Agile
Ideal Days
Paper illustration for Bucket System.
Agile
Bucket System
Purposedifferent
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 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 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
MediumLowLowMedium
Timedifferent
30-90 min2-5 min je Item15-60 min30-90 min
Participantsdifferent
1-63-92-93-12
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Decision Tree, Option Map, Assumption ListRelative Estimates, Assumption Notes, Split CandidatesIdeal Day Estimates, Assumption Notes, Capacity CaveatsBucketed Backlog, Relative Estimates, Split Candidates
Tagsno overlap
DecisionTreeOptions
EstimationAgileRelative sizingTeam
EstimationEffortAgile
EstimationBacklogRelative sizing
Add more methods