View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile Planning Poker |  Architecture Request for Comments |  Architecture Architecture Decision Record |
|---|---|---|---|
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. | 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. | 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. |
Complexitydifferent | Low | Medium | Low |
Timedifferent | 2-5 min je Item | 1-3 Wochen vom Draft bis zur Entscheidung | 15-45 min |
Participantsdifferent | 3-9 | 3-20 Reviewer | 1-3 |
Formatdifferent | Workshop + async | Async | Async |
Outputdifferent | Relative Estimates, Assumption Notes, Split Candidates | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | ADR File, Decision Log, Rationale |
Tagsno overlap | EstimationAgileRelative sizingTeam | ArchitectureDecisionAsyncGovernance | ArchitectureRationaleDocumentationGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
