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 Dot Estimation.
Facilitation
Dot Estimation
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
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 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.arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes.
Complexitydifferent
LowMediumLowLow
Timedifferent
15-45 min30-90 min5-20 min1-2 Tage
Participantsdifferent
1-33-123-201-4
Formatdifferent
AsyncWorkshopWorkshopWorkshop + async
Outputdifferent
ADR File, Decision Log, RationaleAffinity Size Map, Grouped Estimates, Unclear ItemsEffort Heatmap, Risk Signals, Discussion TargetsArchitecture Document, Context View, Runtime View, Deployment View
Tagsno overlap
ArchitectureRationaleDocumentationGovernance
EstimationBacklogRelative sizing
EstimationEffortRisk
ArchitectureDocumentationCommunication
Add more methods