View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile WSJF |  Engineering Kanban |  Decision Making Constraint Analysis |
|---|---|---|---|
Purposedifferent | When many tasks compete for the same capacity, it orders work by economic impact. It makes time lost, benefit, and effort comparable together. | 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. | When an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped. |
Complexitydifferent | High | Medium | Low |
Timedifferent | 45-90 min | Ongoing | 30-90 min |
Participantsdifferent | 3-10 | 2-12 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Ranked Backlog, Cost-of-Delay Assumptions | Kanban board, WIP policies, Flow metrics | Constraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries |
Tagsno overlap | LeanEconomicsSequencePrioritization | FlowVisual managementDelivery | ConstraintsDecisionPlanningOptions |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
