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
A hypothetical failure makes concrete risks, signals, and fitting mitigations visible.
Decision Making
Pre-Mortem
Paper illustration for Bucket System.
Agile
Bucket System
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.In early initiatives with many uncertainties, planning quickly turns too optimistic. A pre-mortem makes the expected failure visible in advance and sharpens the view of causes, gaps, and countermeasures.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
2-5 min je Item30-90 min20–45 min30-90 min
Participantsdifferent
3-91-6Small cross-functional group3-12
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Relative Estimates, Assumption Notes, Split CandidatesDecision Tree, Option Map, Assumption ListRisk list, Mitigation plan, Assumption logBucketed Backlog, Relative Estimates, Split Candidates
Tagsno overlap
EstimationAgileRelative sizingTeam
DecisionTreeOptions
RiskDecisionFailurePlanning
EstimationBacklogRelative sizing
Add more methods