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
Views and Beyond method illustration showing its working structure
Architecture
Views and Beyond
Paper illustration for Affinity Estimation.
Agile
Affinity Estimation
Paper illustration for Planning Poker.
Agile
Planning Poker
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.Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question.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.
Complexitydifferent
LowMediumMediumLow
Timedifferent
15-45 min1-3 Tage30-90 min2-5 min je Item
Participantsdifferent
1-31-43-123-9
Formatdifferent
AsyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
ADR File, Decision Log, RationaleArchitecture Views, Cross-view Notes, RationaleAffinity Size Map, Grouped Estimates, Unclear ItemsRelative Estimates, Assumption Notes, Split Candidates
Tagsno overlap
ArchitectureRationaleDocumentationGovernance
DocumentationStakeholdersArchitecture
EstimationBacklogRelative sizing
EstimationAgileRelative sizingTeam
Add more methods