View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Decision Making Three-Point Estimation |  Architecture C4 Model |  Architecture Architecture Decision Record |  Agile NoEstimates |
|---|---|---|---|---|
Purposedifferent | A single estimate for effort, time, or risk often looks too smooth for the real uncertainty behind it. It separates options, evaluation criteria, and open risks. The result is captured as a Three-Point Estimate, Risk Range, and Assumption Notes. | 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. | 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. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 10-30 min je Item | 1-4 h | 15-45 min | laufend |
Participantsdifferent | 1-8 | 1-5 | 1-3 | 2-12 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + async |
Outputdifferent | Three-Point Estimate, Risk Range, Assumption Notes | Context Diagram, Container Diagram, Component Diagram | ADR File, Decision Log, Rationale | Throughput Data, Flow Forecast, Slicing Rules |
Tagsno overlap | EstimationUncertaintyForecasting | ArchitectureCommunicationVisualization | ArchitectureRationaleDocumentationGovernance | EstimationForecastingFlow |