View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Knowledge Modeling Feynman Technique |  Delivery Value Stream Mapping |  Agile NoEstimates |  Decision Making Three-Point Estimation |
|---|---|---|---|---|
Purposedifferent | The Feynman Technique checks understanding by explaining a topic so that it stays easy for others to understand. It makes knowledge gaps visible before they become costly in everyday work. | 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. | A single estimate for effort, time, or risk often looks too smooth for the real uncertainty behind it. It separates options, evaluation criteria, and open risks. The result is captured as a Three-Point Estimate, Risk Range, and Assumption Notes. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | 20-60 min | 1-3 h | laufend | 10-30 min je Item |
Participantsdifferent | 1 | 4-10 | 2-12 | 1-8 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Plain-language Explanation, Knowledge Gaps, Study Notes | Current-state map, Future-state map, Bottleneck list | Throughput Data, Flow Forecast, Slicing Rules | Three-Point Estimate, Risk Range, Assumption Notes |
Tagsno overlap | LearningKnowledgeUnderstanding | LeanFlowWasteDelivery | EstimationForecastingFlow | EstimationUncertaintyForecasting |