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 Story Points.
Agile
Story Points
Paper illustration for PERT Estimation.
Decision Making
PERT Estimation
Paper illustration for T-Shirt Sizing.
Agile
T-Shirt Sizing
Paper illustration for Dot Estimation.
Facilitation
Dot Estimation
Purposedifferent
When teams want to rate complexity rather than hours, it creates a shared, relative scale. It sorts work by value, risk, and delivery ability. The result is captured as Point Estimates, Reference Stories, and Velocity Data.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 effort only needs to be classified roughly, it makes comparability more important than false precision. It helps sort work quickly into manageable sizes.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
laufend, 1-5 min je Item15-45 min15-45 min5-20 min
Participantsdifferent
3-91-82-123-20
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Point Estimates, Reference Stories, Velocity DataPERT Estimate, Expected Value, Risk NotesSize Buckets, Rough Backlog Map, Split CandidatesEffort Heatmap, Risk Signals, Discussion Targets
Tags1 shared
EstimationAgileMeasurement
EstimationUncertaintyRisk
EstimationAgileRoadmap
EstimationEffortRisk
Add more methods