View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Delivery Value Stream Mapping |  Delivery Monte Carlo Forecasting |  Agile Planning Poker |  Agile Affinity Estimation |
|---|---|---|---|---|
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. | 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 estimates within the team diverge too much, it puts differing expectations on a common test bench. It separates rough complexity from unspoken assumptions. | When many tasks need to be classified quickly, it sorts them by perceived effort and similarity. It reduces the effort of fine-grained estimation for large volumes. |
Complexitydifferent | Medium | High | Low | Medium |
Timedifferent | 1-3 h | 30-90 min Setup, danach laufend | 2-5 min je Item | 30-90 min |
Participantsdifferent | 4-10 | 1-8 | 3-9 | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | Forecast Percentiles, Throughput Dataset, Risk Communication | Relative Estimates, Assumption Notes, Split Candidates | Affinity Size Map, Grouped Estimates, Unclear Items |
Tagsno overlap | LeanFlowWasteDelivery | ForecastingFlowDelivery | EstimationAgileRelative sizingTeam | EstimationBacklogRelative sizing |