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 Argument Mapping
Decision Making
Argument Mapping
Paper illustration for Affinity Estimation.
Agile
Affinity Estimation
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Purposedifferent
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.An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale.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.
Complexitydifferent
MediumMediumMediumLow
Timedifferent
1-3 h30-90 min1-3 Wochen vom Draft bis zur Entscheidung15-45 min
Participantsdifferent
1-83-123-20 Reviewer1-3
Formatdifferent
Workshop + asyncWorkshopAsyncAsync
Outputdifferent
Argument Map, Evidence Gaps, Decision RationaleAffinity Size Map, Grouped Estimates, Unclear ItemsRFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsADR File, Decision Log, Rationale
Tagsno overlap
SensemakingDecisionRationale
EstimationBacklogRelative sizing
ArchitectureDecisionAsyncGovernance
ArchitectureRationaleDocumentationGovernance
Add more methods