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 MappingDot EstimationLASR (Lightweight Approach for Software Reviews)ATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Delivery Value Stream Mapping |  Facilitation Dot Estimation |  Architecture LASR (Lightweight Approach for Software Reviews) |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|---|
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. | When size or effort can only be estimated roughly, Dot Estimation condenses the group's experience into a quick range. It turns individual contributions into a visible selection. The result is captured as an Effort Heatmap, Risk Signals, and Discussion Targets. | 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. | 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 | 1-3 h | 5-20 min | 3–4 h for initial assessment; preparation and deeper analysis additional | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 4-10 | 3-20 | 1 or a small team; particularly suitable for 3–4 people | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | Effort Heatmap, Risk Signals, Discussion Targets | 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 | 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 | LeanFlowWasteDelivery | EstimationEffortRisk | ArchitectureQualityRiskAssessmentLean | ArchitectureQualityRiskTradeoffsStakeholders |