View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Facilitation Dot Estimation |  Delivery Value Stream Mapping |  Architecture Architecture Decision Record |  Agile Ideal Days |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | When effort needs to be thought of as real working time, it offers a simple common denominator for comparison. It sorts work by value, risk, and delivery ability. The result is captured as Ideal Day Estimates, Assumption Notes, and Capacity Caveats. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 5-20 min | 1-3 h | 15-45 min | 15-60 min |
Participantsdifferent | 3-20 | 4-10 | 1-3 | 2-9 |
Formatdifferent | Workshop | Workshop | Async | Workshop + async |
Outputdifferent | Effort Heatmap, Risk Signals, Discussion Targets | Current-state map, Future-state map, Bottleneck list | ADR File, Decision Log, Rationale | Ideal Day Estimates, Assumption Notes, Capacity Caveats |
Tagsno overlap | EstimationEffortRisk | LeanFlowWasteDelivery | ArchitectureRationaleDocumentationGovernance | EstimationEffortAgile |