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 of a horizontal story map with an activity backbone, task cards below it and a cross-map release line.
Product Discovery
User Story Mapping
Paper illustration for Affinity Estimation.
Agile
Affinity Estimation
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 user goals and delivery scope could drift apart, it orders the journey from goal to slice. It makes visible where an MVP can genuinely be cut.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.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
MediumMediumLowLow
Timedifferent
2-4 h30-90 min20–45 min5-20 min
Participantsdifferent
4-103-12Small cross-functional group3-20
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Story Map, Release Slices, Backlog CandidatesAffinity Size Map, Grouped Estimates, Unclear ItemsRisk list, Mitigation plan, Assumption logEffort Heatmap, Risk Signals, Discussion Targets
Tagsno overlap
BacklogJourneyPlanningMVP
EstimationBacklogRelative sizing
RiskDecisionFailurePlanning
EstimationEffortRisk
Add more methods