View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Engineering Kanban |  Architecture C4 Model |  Agile NoEstimates |  Architecture arc42 |
|---|---|---|---|---|
Purposedifferent | 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. | 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 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. | 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 | Low | Medium | Low |
Timedifferent | Ongoing | 1-4 h | laufend | 1-2 Tage |
Participantsdifferent | 2-12 | 1-5 | 2-12 | 1-4 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Kanban board, WIP policies, Flow metrics | Context Diagram, Container Diagram, Component Diagram | Throughput Data, Flow Forecast, Slicing Rules | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | FlowVisual managementDelivery | ArchitectureCommunicationVisualization | EstimationForecastingFlow | ArchitectureDocumentationCommunication |