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 Bucket System.
Agile
Bucket System
Paper illustration for Argument Mapping
Decision Making
Argument Mapping
Paper illustration for Affinity Estimation.
Agile
Affinity Estimation
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 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.When statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on.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
LowMediumMediumMedium
Timedifferent
15-45 min30-90 min1-3 h30-90 min
Participantsdifferent
1-33-121-83-12
Formatdifferent
AsyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
ADR File, Decision Log, RationaleBucketed Backlog, Relative Estimates, Split CandidatesArgument Map, Evidence Gaps, Decision RationaleAffinity Size Map, Grouped Estimates, Unclear Items
Tagsno overlap
ArchitectureRationaleDocumentationGovernance
EstimationBacklogRelative sizing
SensemakingDecisionRationale
EstimationBacklogRelative sizing
Add more methods