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 Architecture Decision Record |  Engineering Kanban |  Architecture Views and Beyond |  Delivery Monte Carlo Forecasting |
|---|---|---|---|---|
Purposedifferent | 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 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. | Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question. | 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. |
Complexitydifferent | Low | Medium | Medium | High |
Timedifferent | 15-45 min | Ongoing | 1-3 Tage | 30-90 min Setup, danach laufend |
Participantsdifferent | 1-3 | 2-12 | 1-4 | 1-8 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Kanban board, WIP policies, Flow metrics | Architecture Views, Cross-view Notes, Rationale | Forecast Percentiles, Throughput Dataset, Risk Communication |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | FlowVisual managementDelivery | DocumentationStakeholdersArchitecture | ForecastingFlowDelivery |