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 Architecture Decision Record |  Decision Making Three-Point Estimation |  Decision Making PERT Estimation |
|---|---|---|---|---|
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. | 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. | 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. | On complex initiatives, a plain average tends to understate just how uncertain the outcome really is. It separates options, evaluation criteria, and open risks. The result is captured as a PERT Estimate, Expected Value, and Risk Notes. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | Ongoing | 15-45 min | 10-30 min je Item | 15-45 min |
Participantsdifferent | 2-12 | 1-3 | 1-8 | 1-8 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | Kanban board, WIP policies, Flow metrics | ADR File, Decision Log, Rationale | Three-Point Estimate, Risk Range, Assumption Notes | PERT Estimate, Expected Value, Risk Notes |
Tagsno overlap | FlowVisual managementDelivery | ArchitectureRationaleDocumentationGovernance | EstimationUncertaintyForecasting | EstimationUncertaintyRisk |