View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Operations ABC Analysis | ![]() Delivery Monte Carlo Forecasting | ![]() Agile Start Stop Continue | ![]() Agile 4Ls Retrospective |
|---|---|---|---|---|
Purposedifferent | With many similar objects of differing economic significance, the method prioritizes effort by effect. It separates what needs regular steering from what rarely needs attention. | 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 a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. | When a sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time. |
Complexitydifferent | Low | High | Low | Low |
Timedifferent | 30-60 min | 30-90 min Setup, danach laufend | 30-60 min | 45–75 min |
Participantsdifferent | 1-5 | 1-8 | 3-12 | Team members involved |
Formatdifferent | Async | Workshop + async | Workshop | Workshop |
Outputdifferent | ABC Classification, Focus Rules, Control List | Forecast Percentiles, Throughput Dataset, Risk Communication | Start Stop Continue Board, Improvement Actions | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | PrioritizationOperationsPortfolio | ForecastingFlowDelivery | RetrospectiveImprovementTeamReflection | RetrospectiveLearningReflectionTeam |



