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 of Scrum with its method-specific working model.
Agile
Scrum
Paper illustration for Affinity Estimation.
Agile
Affinity Estimation
Story Splitting method illustration showing its working structure
Agile
Story Splitting
Paper illustration for Ideal Days.
Agile
Ideal Days
Purposedifferent
When a team needs to work in a fixed delivery rhythm, it stabilizes cadence, responsibility, and feedback loops. It makes collaboration reliable across sprint boundaries.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 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 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.
Complexitydifferent
MediumMediumMediumLow
Timedifferent
1-4 Wochen je Sprint, laufend30-90 min30-60 min15-60 min
Participantsdifferent
3-10 (Scrum Team)3-122-62-9
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Product Backlog, Sprint Backlog, Increment, Sprint GoalAffinity Size Map, Grouped Estimates, Unclear ItemsSmaller Stories, Acceptance Criteria, Split RationaleIdeal Day Estimates, Assumption Notes, Capacity Caveats
Tagsno overlap
AgileIterationCadence
EstimationBacklogRelative sizing
BacklogIterationDelivery
EstimationEffortAgile
Add more methods