View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Business Strategy VMGS |  Delivery RAID Log |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Facilitation Alignment Mapping |
|---|---|---|---|---|
Purposedifferent | VMGS arranges vision, mission, goals, and strategies into a clear guiding logic. Direction, purpose, and priorities are connected so teams can decide more coherently. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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. | 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 | Medium | Low | High | Medium |
Timedifferent | 2-4 h | 30 min Setup, dann laufend | Several meetings plus preparation and analysis; total effort depends on scope | 1-2 h |
Participantsdifferent | 3-12 | 1-3 maintaining, briefing for everyone | Evaluation team, architects, and relevant stakeholders | 4-12 |
Formatdifferent | Workshop | Async | Workshop + async | Workshop |
Outputdifferent | Vision Statement, Mission Statement, Goals, Strategies | RAID Log, Status Report Source | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | VisionGoalsStrategy | RiskTrackingStakeholdersGovernance | ArchitectureQualityRiskTradeoffsStakeholders | AlignmentStakeholdersStrategyFacilitation |