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 Quality Attribute Workshop |  Agile WSJF |  Facilitation Stakeholder Mapping |  Architecture Software Architecture Canvas |
|---|---|---|---|---|
Purposedifferent | A Quality Attribute Workshop translates quality requirements into concrete scenarios and architecture impulses. The method brings product, engineering, and operations to the same view of desired properties. | 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. | The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly. |
Complexitydifferent | Medium | High | Low | Low |
Timedifferent | 2-4 h | 45-90 min | 60–90 min | 1-2 h |
Participantsdifferent | 5-15 | 3-10 | 2-8 | 3-10 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Quality Scenarios, Priority List, Architecture Concerns | Ranked Backlog, Cost-of-Delay Assumptions | Stakeholder Map, Engagement Plan, Risk Notes | Architecture Canvas, Goals, Constraints, Quality Attributes |
Tagsno overlap | RequirementsArchitectureWorkshop | LeanEconomicsSequencePrioritization | StakeholdersAlignmentFacilitationChange | CanvasArchitectureAlignmentWorkshop |