View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture arc42 |  Agile Planning Poker |  Architecture Architecture Decision Record |  Agile Affinity Estimation |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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 | Low | Low | Low | Medium |
Timedifferent | 1-2 Tage | 2-5 min je Item | 15-45 min | 30-90 min |
Participantsdifferent | 1-4 | 3-9 | 1-3 | 3-12 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop |
Outputdifferent | Architecture Document, Context View, Runtime View, Deployment View | Relative Estimates, Assumption Notes, Split Candidates | ADR File, Decision Log, Rationale | Affinity Size Map, Grouped Estimates, Unclear Items |
Tagsno overlap | ArchitectureDocumentationCommunication | EstimationAgileRelative sizingTeam | ArchitectureRationaleDocumentationGovernance | EstimationBacklogRelative sizing |