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 Affinity Estimation.
Agile
Affinity Estimation
Paper illustration for PERT Estimation.
Decision Making
PERT Estimation
Paper illustration for Planning Poker.
Agile
Planning Poker
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.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.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 estimates within the team diverge too much, it puts differing expectations on a common test bench. It separates rough complexity from unspoken assumptions.
Complexitydifferent
MediumMediumMediumLow
Timedifferent
laufend, 1-5 min je Item30-90 min15-45 min2-5 min je Item
Participantsdifferent
3-93-121-83-9
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Point Estimates, Reference Stories, Velocity DataAffinity Size Map, Grouped Estimates, Unclear ItemsPERT Estimate, Expected Value, Risk NotesRelative Estimates, Assumption Notes, Split Candidates
Tags1 shared
EstimationAgileMeasurement
EstimationBacklogRelative sizing
EstimationUncertaintyRisk
EstimationAgileRelative sizingTeam
Add more methods