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 Architecture Decision Record |  Agile Planning Poker |  Architecture Request for Comments |  Agile Affinity Estimation |
|---|---|---|---|---|
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 estimates within the team diverge too much, it puts differing expectations on a common test bench. It separates rough complexity from unspoken assumptions. | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. | 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 | Medium | Medium |
Timedifferent | 15-45 min | 2-5 min je Item | 1-3 Wochen vom Draft bis zur Entscheidung | 30-90 min |
Participantsdifferent | 1-3 | 3-9 | 3-20 Reviewer | 3-12 |
Formatdifferent | Async | Workshop + async | Async | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Relative Estimates, Assumption Notes, Split Candidates | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Affinity Size Map, Grouped Estimates, Unclear Items |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | EstimationAgileRelative sizingTeam | ArchitectureDecisionAsyncGovernance | EstimationBacklogRelative sizing |