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 |  Architecture SAAM (Software Architecture Analysis Method) |  Decision Making Force Field Analysis |  Delivery Cost of Delay |
|---|---|---|---|---|
Purposedifferent | When many tasks compete for the same capacity, it orders work by economic impact. It makes time lost, benefit, and effort comparable together. | SAAM helps teams judge an architecture’s suitability for selected tasks and changes. It is particularly useful for examining modifiability and comparing architecture alternatives with clear reasoning. | In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving. | Helps clarify scope, order, and delivery flow in concrete terms. It makes work, constraints, and sequence manageable. The result is captured as a Cost of Delay table and prioritization sequence. |
Complexitydifferent | High | High | Low | High |
Timedifferent | 45-90 min | Preparation, scenario analysis, and findings review; effort depends on scope | 45-90 min | 90-180 min |
Participantsdifferent | 3-10 | Architecture experts and stakeholders for scenarios and weighting | 3-12 | 3-8 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Ranked Backlog, Cost-of-Delay Assumptions | Domain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternatives | Force Field Map, Change Levers, Risk Notes | CoD Table, Prioritization Sequence |
Tagsno overlap | LeanEconomicsSequencePrioritization | ArchitectureChangeAnalysisComparisonQuality | ChangeDecisionStrategy | PrioritizationDeliveryEconomicsDecision |