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 Teach-back |  Agile NoEstimates |  Delivery Monte Carlo Forecasting |  Knowledge Modeling Feynman Technique |
|---|---|---|---|---|
Purposedifferent | Teach-back checks whether an explanation actually got through to the other person. The method makes misunderstandings visible early and strengthens shared understanding in advisory and learning situations. | 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. | 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. | 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. |
Complexitydifferent | Low | Medium | High | Low |
Timedifferent | 5-20 min | laufend | 30-90 min Setup, danach laufend | 20-60 min |
Participantsdifferent | 2-8 | 2-12 | 1-8 | 1 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Async |
Outputdifferent | Understanding Check, Clarification Notes, Learning Gaps | Throughput Data, Flow Forecast, Slicing Rules | Forecast Percentiles, Throughput Dataset, Risk Communication | Plain-language Explanation, Knowledge Gaps, Study Notes |
Tagsno overlap | LearningUnderstandingCommunication | EstimationForecastingFlow | ForecastingFlowDelivery | LearningKnowledgeUnderstanding |