View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Delivery Cost of Delay |  Decision Making Pareto Analysis |  Architecture SAAM (Software Architecture Analysis Method) |  Operations Eat the Frog |
|---|---|---|---|---|
Purposedifferent | 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. | In many problem situations, effect is distributed unequally across many causes. A Pareto Analysis separates the few drivers with high leverage from the long remainder and focuses attention on what measurably moves the needle. | 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. | The method protects energy and attention for the task that creates the largest progress and is often postponed. |
Complexitydifferent | High | Low | High | Low |
Timedifferent | 90-180 min | 30-60 min | Preparation, scenario analysis, and findings review; effort depends on scope | 15-90 min daily |
Participantsdifferent | 3-8 | 1-6 | Architecture experts and stakeholders for scenarios and weighting | 1 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Async |
Outputdifferent | CoD Table, Prioritization Sequence | Pareto Chart, Top Causes, Focus List | 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 | Priority Task, Completion Note, Daily Focus |
Tagsno overlap | PrioritizationDeliveryEconomicsDecision | PrioritizationQualityFocusRoot cause | ArchitectureChangeAnalysisComparisonQuality | PrioritizationProductivityFocusExecution |