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 NoEstimates.
Agile
NoEstimates
Paper illustration for Ideal Days.
Agile
Ideal Days
Paper illustration for Planning Poker.
Agile
Planning Poker
Paper illustration for Affinity Estimation.
Agile
Affinity Estimation
Purposedifferent
When estimating slows a team down more than it helps, it shifts the focus to flow, small slices, and real lead time. It sorts work by value, risk, and delivery ability. The result is captured as Throughput Data, Flow Forecast, and Slicing Rules.When effort needs to be thought of as real working time, it offers a simple common denominator for comparison. It sorts work by value, risk, and delivery ability. The result is captured as Ideal Day Estimates, Assumption Notes, and Capacity Caveats.When estimates within the team diverge too much, it puts differing expectations on a common test bench. It separates rough complexity from unspoken assumptions.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.
Complexitydifferent
MediumLowLowMedium
Timedifferent
laufend15-60 min2-5 min je Item30-90 min
Participantsdifferent
2-122-93-93-12
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Throughput Data, Flow Forecast, Slicing RulesIdeal Day Estimates, Assumption Notes, Capacity CaveatsRelative Estimates, Assumption Notes, Split CandidatesAffinity Size Map, Grouped Estimates, Unclear Items
Tags1 shared
EstimationForecastingFlow
EstimationEffortAgile
EstimationAgileRelative sizingTeam
EstimationBacklogRelative sizing
Add more methods