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
Story Splitting method illustration showing its working structure
Agile
Story Splitting
Paper illustration for PERT Estimation.
Decision Making
PERT Estimation
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 a story becomes too large for a clean flow, it breaks scope down along value and risk. It shapes the work into a form that ships earlier and is easier to verify.On complex initiatives, a plain average tends to understate just how uncertain the outcome really is. It separates options, evaluation criteria, and open risks. The result is captured as a PERT Estimate, Expected Value, and Risk Notes.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
MediumMediumMediumLow
Timedifferent
30-90 min30-60 min15-45 min5-20 min
Participantsdifferent
3-122-61-83-20
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Affinity Size Map, Grouped Estimates, Unclear ItemsSmaller Stories, Acceptance Criteria, Split RationalePERT Estimate, Expected Value, Risk NotesEffort Heatmap, Risk Signals, Discussion Targets
Tagsno overlap
EstimationBacklogRelative sizing
BacklogIterationDelivery
EstimationUncertaintyRisk
EstimationEffortRisk
Add more methods