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 ATAM (Architecture Tradeoff Analysis Method) |  Knowledge Modeling Concept Mapping |  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. | ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation. | Concept Mapping arranges terms and relationships in a network that makes subject-matter connections tangible. It fits when a topic needs to be understood structurally rather than linearly. | 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 | Medium | High |
Timedifferent | 45-90 min | Several meetings plus preparation and analysis; total effort depends on scope | 1-2 h | 90-180 min |
Participantsdifferent | 3-10 | Evaluation team, architects, and relevant stakeholders | 1-8 | 3-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Ranked Backlog, Cost-of-Delay Assumptions | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Concept Map, Relationship Labels, Knowledge Gaps | CoD Table, Prioritization Sequence |
Tagsno overlap | LeanEconomicsSequencePrioritization | ArchitectureQualityRiskTradeoffsStakeholders | KnowledgeConceptsMappingSensemaking | PrioritizationDeliveryEconomicsDecision |