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 Affinity Estimation.
Agile
Affinity Estimation
Paper illustration for Planning Poker.
Agile
Planning Poker
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Purposedifferent
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 estimates within the team diverge too much, it puts differing expectations on a common test bench. It separates rough complexity from unspoken assumptions.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.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
MediumLowLowLow
Timedifferent
30-90 min2-5 min je Item15-45 min1-2 Tage
Participantsdifferent
3-123-91-31-4
Formatdifferent
WorkshopWorkshop + asyncAsyncWorkshop + async
Outputdifferent
Affinity Size Map, Grouped Estimates, Unclear ItemsRelative Estimates, Assumption Notes, Split CandidatesADR File, Decision Log, RationaleArchitecture Document, Context View, Runtime View, Deployment View
Tagsno overlap
EstimationBacklogRelative sizing
EstimationAgileRelative sizingTeam
ArchitectureRationaleDocumentationGovernance
ArchitectureDocumentationCommunication
Add more methods