View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Product Discovery Kano Model |  Delivery Monte Carlo Forecasting |  Delivery Value Stream Mapping |  Agile NoEstimates |
|---|---|---|---|---|
Purposedifferent | When features need to be distinguished by their effect on satisfaction, it makes expectations and surprises comparable. It separates basic needs, performance contribution, and delight. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as Forecast Percentiles, Throughput Dataset, and Risk Communication. | 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 estimating slows a team down more than it helps, it shifts the focus to flow, small slices, and real lead time. It sorts work by value, risk, and delivery ability. The result is captured as Throughput Data, Flow Forecast, and Slicing Rules. |
Complexitydifferent | Medium | High | Medium | Medium |
Timedifferent | 1-2 Tage | 30-90 min Setup, danach laufend | 1-3 h | laufend |
Participantsdifferent | 10-50 | 1-8 | 4-10 | 2-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Kano Matrix, Feature Classes, Priority Themes | Forecast Percentiles, Throughput Dataset, Risk Communication | Current-state map, Future-state map, Bottleneck list | Throughput Data, Flow Forecast, Slicing Rules |
Tagsno overlap | SatisfactionPrioritizationCustomer | ForecastingFlowDelivery | LeanFlowWasteDelivery | EstimationForecastingFlow |