View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Bottleneck Analysis |  Agile NoEstimates |  Architecture Architecture Decision Record |  Architecture arc42 |
|---|---|---|---|---|
Purposedifferent | For a flow that backs up at one point, the method looks for the capacity limit with the greatest leverage. It explains why extra effort elsewhere barely improves throughput. | 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. | 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. | 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. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 1-3 h | laufend | 15-45 min | 1-2 Tage |
Participantsdifferent | 3-8 | 2-12 | 1-3 | 1-4 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + async |
Outputdifferent | Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures | Throughput Data, Flow Forecast, Slicing Rules | ADR File, Decision Log, Rationale | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | FlowMeasurementConstraints | EstimationForecastingFlow | ArchitectureRationaleDocumentationGovernance | ArchitectureDocumentationCommunication |