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 Dot Estimation.
Facilitation
Dot Estimation
Paper illustration for Ideal Days.
Agile
Ideal Days
Paper illustration of a MoSCoW board with four columns and a visible release boundary.
Delivery
MoSCoW
Paper illustration of ICE Scoring with its method-specific working model.
Product Strategy
ICE Scoring
Purposedifferent
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.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 a release carries too many demands and priorities are only ever negotiated, MoSCoW creates clear boundaries for the next cut. Must, Should, Could, and Won't make commitment, room for maneuver, and trade-off logic visible to everyone involved.When ideas need sorting quickly, it condenses impact, confidence, and effort into one compact score. It connects customer value, product logic, and decision priorities. The result is captured as an ICE table and top-ideas list.
Complexitysame
LowLowLowLow
Timedifferent
5-20 min15-60 min30-90 min30-60 min
Participantsdifferent
3-202-93-122-8
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Effort Heatmap, Risk Signals, Discussion TargetsIdeal Day Estimates, Assumption Notes, Capacity CaveatsPrioritized Backlog, Release Scope, Tradeoff NotesICE Table, Top Idea List
Tagsno overlap
EstimationEffortRisk
EstimationEffortAgile
PrioritizationScopeDecision
PrioritizationScoringGrowthDecision
Add more methods