View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture SAAM (Software Architecture Analysis Method) |  Agile WSJF |  Facilitation Stakeholder Mapping |  Facilitation Alignment Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | When many tasks compete for the same capacity, it orders work by economic impact. It makes time lost, benefit, and effort comparable together. | When an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. | When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. |
Complexitydifferent | High | High | Low | Medium |
Timedifferent | Preparation, scenario analysis, and findings review; effort depends on scope | 45-90 min | 60–90 min | 1-2 h |
Participantsdifferent | Architecture experts and stakeholders for scenarios and weighting | 3-10 | 2-8 | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | 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 | Ranked Backlog, Cost-of-Delay Assumptions | Stakeholder Map, Engagement Plan, Risk Notes | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | ArchitectureChangeAnalysisComparisonQuality | LeanEconomicsSequencePrioritization | StakeholdersAlignmentFacilitationChange | AlignmentStakeholdersStrategyFacilitation |