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 two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Paper illustration for Affinity Estimation.
Agile
Affinity Estimation
Paper illustration for Ideal Days.
Agile
Ideal Days
Paper illustration for Bucket System.
Agile
Bucket System
Purposedifferent
An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable.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 a large batch of work needs a fast, rough estimate, it sorts items into predefined size buckets. It sorts work by value, risk, and delivery ability. The result is captured as a Bucketed Backlog, Relative Estimates, and Split Candidates.
Complexitydifferent
LowMediumLowMedium
Timedifferent
15-45 min30-90 min15-60 min30-90 min
Participantsdifferent
1-33-122-93-12
Formatdifferent
AsyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
ADR File, Decision Log, RationaleAffinity Size Map, Grouped Estimates, Unclear ItemsIdeal Day Estimates, Assumption Notes, Capacity CaveatsBucketed Backlog, Relative Estimates, Split Candidates
Tagsno overlap
ArchitectureRationaleDocumentationGovernance
EstimationBacklogRelative sizing
EstimationEffortAgile
EstimationBacklogRelative sizing
Add more methods