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 |  Business Strategy VRIO Framework |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|---|
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. | The VRIO Framework rates resources and capabilities on whether they are Valuable, Rare, Inimitable, and Organized. It compares strengths, risks, market logic, and courses of action. The result is captured as a VRIO table and strategic actions. | 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. |
Complexitydifferent | Medium | Low | Medium | High |
Timedifferent | 2-4 h | 30 min Setup, dann laufend | 90-180 min | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 3-12 | 1-3 maintaining, briefing for everyone | 3-6 | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Workshop | Async | Workshop | Workshop + async |
Outputdifferent | Vision Statement, Mission Statement, Goals, Strategies | RAID Log, Status Report Source | VRIO Table, Strategic Actions | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations |
Tagsno overlap | VisionGoalsStrategy | RiskTrackingStakeholdersGovernance | StrategyDiagnosisBusiness modelCapability | ArchitectureQualityRiskTradeoffsStakeholders |