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 NoEstimates |  Architecture arc42 |  Architecture Request for Comments |
|---|---|---|---|---|
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 estimating slows a team down more than it helps, it shifts the focus to flow, small slices, and real lead time. It sorts work by value, risk, and delivery ability. The result is captured as Throughput Data, Flow Forecast, and Slicing Rules. | 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. | 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. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 15-45 min | laufend | 1-2 Tage | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | 1-3 | 2-12 | 1-4 | 3-20 Reviewer |
Formatdifferent | Async | Workshop + async | Workshop + async | Async |
Outputdifferent | ADR File, Decision Log, Rationale | Throughput Data, Flow Forecast, Slicing Rules | Architecture Document, Context View, Runtime View, Deployment View | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | EstimationForecastingFlow | ArchitectureDocumentationCommunication | ArchitectureDecisionAsyncGovernance |