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 Planning Poker.
Agile
Planning Poker
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
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
Purposedifferent
When estimates within the team diverge too much, it puts differing expectations on a common test bench. It separates rough complexity from unspoken assumptions.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.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.
Complexitydifferent
LowLowLowMedium
Timedifferent
2-5 min je Item1-2 Tage15-45 min30-90 min
Participantsdifferent
3-91-41-33-12
Formatdifferent
Workshop + asyncWorkshop + asyncAsyncWorkshop
Outputdifferent
Relative Estimates, Assumption Notes, Split CandidatesArchitecture Document, Context View, Runtime View, Deployment ViewADR File, Decision Log, RationaleAffinity Size Map, Grouped Estimates, Unclear Items
Tagsno overlap
EstimationAgileRelative sizingTeam
ArchitectureDocumentationCommunication
ArchitectureRationaleDocumentationGovernance
EstimationBacklogRelative sizing
Add more methods