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
Story Splitting method illustration showing its working structure
Agile
Story Splitting
Paper illustration for Affinity Estimation.
Agile
Affinity Estimation
Paper illustration for Ideal Days.
Agile
Ideal Days
Paper illustration for Dot Estimation.
Facilitation
Dot Estimation
Purposedifferent
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.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 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 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
30-60 min30-90 min15-60 min5-20 min
Participantsdifferent
2-63-122-93-20
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
Smaller Stories, Acceptance Criteria, Split RationaleAffinity Size Map, Grouped Estimates, Unclear ItemsIdeal Day Estimates, Assumption Notes, Capacity CaveatsEffort Heatmap, Risk Signals, Discussion Targets
Tagsno overlap
BacklogIterationDelivery
EstimationBacklogRelative sizing
EstimationEffortAgile
EstimationEffortRisk
Add more methods