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 |  Delivery Monte Carlo Forecasting |  Agile NoEstimates |  Engineering Kanban |
|---|---|---|---|---|
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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as Forecast Percentiles, Throughput Dataset, and Risk Communication. | 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. | When work sits in too many parallel streams, throughput suffers and no one sees the bottlenecks. Kanban makes the flow of work visible and limits overload so a system becomes calmer and more predictable. |
Complexitydifferent | Low | High | Medium | Medium |
Timedifferent | 1-4 h | 30-90 min Setup, danach laufend | laufend | Ongoing |
Participantsdifferent | 1-5 | 1-8 | 2-12 | 2-12 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | Forecast Percentiles, Throughput Dataset, Risk Communication | Throughput Data, Flow Forecast, Slicing Rules | Kanban board, WIP policies, Flow metrics |
Tagsno overlap | ArchitectureCommunicationVisualization | ForecastingFlowDelivery | EstimationForecastingFlow | FlowVisual managementDelivery |