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 Affinity Estimation.
Agile
Affinity Estimation
Paper illustration for Planning Poker.
Agile
Planning Poker
A hypothetical failure makes concrete risks, signals, and fitting mitigations visible.
Decision Making
Pre-Mortem
Paper illustration for Dot Estimation.
Facilitation
Dot Estimation
Purposedifferent
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.When estimates within the team diverge too much, it puts differing expectations on a common test bench. It separates rough complexity from unspoken assumptions.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 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.
Complexitydifferent
MediumLowLowLow
Timedifferent
30-90 min2-5 min je Item20–45 min5-20 min
Participantsdifferent
3-123-9Small cross-functional group3-20
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop
Outputdifferent
Affinity Size Map, Grouped Estimates, Unclear ItemsRelative Estimates, Assumption Notes, Split CandidatesRisk list, Mitigation plan, Assumption logEffort Heatmap, Risk Signals, Discussion Targets
Tagsno overlap
EstimationBacklogRelative sizing
EstimationAgileRelative sizingTeam
RiskDecisionFailurePlanning
EstimationEffortRisk
Add more methods