View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Value Stream MappingATAM (Architecture Tradeoff Analysis Method)A3 Problem SolvingLASR (Lightweight Approach for Software Reviews)
| Criterion |  Delivery Value Stream Mapping |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Operations A3 Problem Solving |  Architecture LASR (Lightweight Approach for Software Reviews) |
|---|---|---|---|---|
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. | For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. | LASR helps development teams identify where their software falls short of important quality goals and which improvements to consider. A small group with existing system knowledge can make an initial assessment and investigate open questions in more detail. |
Complexitydifferent | Medium | High | Medium | Medium |
Timedifferent | 1-3 h | Several meetings plus preparation and analysis; total effort depends on scope | 45-90 min | 3–4 h for initial assessment; preparation and deeper analysis additional |
Participantsdifferent | 4-10 | Evaluation team, architects, and relevant stakeholders | 2-5 | 1 or a small team; particularly suitable for 3–4 people |
Formatdifferent | Workshop | Workshop + async | 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 | A3 Report, Action Plan, Root Cause Analysis | Lean Mission Statement describing the software’s purpose, Prioritized quality goals and evaluation criteria, Risks and estimated gaps against quality goals, More closely examined findings and open checks |
Tagsno overlap | LeanFlowWasteDelivery | ArchitectureQualityRiskTradeoffsStakeholders | LeanProblem solvingCoachingOperations | ArchitectureQualityRiskAssessmentLean |