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 C4 Model |  Agile Affinity Estimation |  Architecture Architecture Decision Record |  Agile Planning Poker |
|---|---|---|---|---|
Purposedifferent | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | 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. | 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. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 1-4 h | 30-90 min | 15-45 min | 2-5 min je Item |
Participantsdifferent | 1-5 | 3-12 | 1-3 | 3-9 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop + async |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | Affinity Size Map, Grouped Estimates, Unclear Items | ADR File, Decision Log, Rationale | Relative Estimates, Assumption Notes, Split Candidates |
Tagsno overlap | ArchitectureCommunicationVisualization | EstimationBacklogRelative sizing | ArchitectureRationaleDocumentationGovernance | EstimationAgileRelative sizingTeam |