View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile Story Points |  Delivery Value Stream Mapping |  Agile Ideal Days |
|---|---|---|---|
Purposedifferent | When teams want to rate complexity rather than hours, it creates a shared, relative scale. It sorts work by value, risk, and delivery ability. The result is captured as Point Estimates, Reference Stories, and Velocity Data. | 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 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 | Medium | Medium | Low |
Timedifferent | laufend, 1-5 min je Item | 1-3 h | 15-60 min |
Participantsdifferent | 3-9 | 4-10 | 2-9 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Point Estimates, Reference Stories, Velocity Data | Current-state map, Future-state map, Bottleneck list | Ideal Day Estimates, Assumption Notes, Capacity Caveats |
Tagsno overlap | EstimationAgileMeasurement | LeanFlowWasteDelivery | EstimationEffortAgile |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
