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 Ideal Days |  Architecture arc42 |  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. | When effort needs to be thought of as real working time, it offers a simple common denominator for comparison. It sorts work by value, risk, and delivery ability. The result is captured as Ideal Day Estimates, Assumption Notes, and Capacity Caveats. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 15-45 min | 15-60 min | 1-2 Tage | 2-5 min je Item |
Participantsdifferent | 1-3 | 2-9 | 1-4 | 3-9 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Ideal Day Estimates, Assumption Notes, Capacity Caveats | Architecture Document, Context View, Runtime View, Deployment View | Relative Estimates, Assumption Notes, Split Candidates |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | EstimationEffortAgile | ArchitectureDocumentationCommunication | EstimationAgileRelative sizingTeam |