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
Paper illustration for Bucket System.
Agile
Bucket System
A hypothetical failure makes concrete risks, signals, and fitting mitigations visible.
Decision Making
Pre-Mortem
Paper illustration for Affinity Estimation.
Agile
Affinity Estimation
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.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.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 many tasks need to be classified quickly, it sorts them by perceived effort and similarity. It reduces the effort of fine-grained estimation for large volumes.
Complexitydifferent
LowMediumLowMedium
Timedifferent
2-5 min je Item30-90 min20–45 min30-90 min
Participantsdifferent
3-93-12Small cross-functional group3-12
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Relative Estimates, Assumption Notes, Split CandidatesBucketed Backlog, Relative Estimates, Split CandidatesRisk list, Mitigation plan, Assumption logAffinity Size Map, Grouped Estimates, Unclear Items
Tagsno overlap
EstimationAgileRelative sizingTeam
EstimationBacklogRelative sizing
RiskDecisionFailurePlanning
EstimationBacklogRelative sizing
Add more methods