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 Value Stream Mapping |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Architecture Views and Beyond |
|---|---|---|---|
Purposedifferent | When delivery work dissolves into wait times, handoffs, and hidden effort, Value Stream Mapping makes the actual flow visible. The method exposes bottlenecks, idle time, and feedback loops so lead time and improvement levers become tangible. | 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. | Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question. |
Complexitydifferent | Medium | High | Medium |
Timedifferent | 1-3 h | Several meetings plus preparation and analysis; total effort depends on scope | 1-3 Tage |
Participantsdifferent | 4-10 | Evaluation team, architects, and relevant stakeholders | 1-4 |
Formatdifferent | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Architecture Views, Cross-view Notes, Rationale |
Tagsno overlap | LeanFlowWasteDelivery | ArchitectureQualityRiskTradeoffsStakeholders | DocumentationStakeholdersArchitecture |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
