View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Engineering Kanban |  Agile Example Mapping |  Agile Three Amigos |  Delivery Monte Carlo Forecasting |
|---|---|---|---|---|
Purposedifferent | When work sits in too many parallel streams, throughput suffers and no one sees the bottlenecks. Kanban makes the flow of work visible and limits overload so a system becomes calmer and more predictable. | When a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. | When story, test, and implementation could drift apart, it brings business perspective, engineering, and quality together early. It prevents a story from being read differently only late in the process. | 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. |
Complexitydifferent | Medium | Low | Low | High |
Timedifferent | Ongoing | 30-60 min | 15-30 min | 30-90 min Setup, danach laufend |
Participantsdifferent | 2-12 | 3-7 | 3 | 1-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Kanban board, WIP policies, Flow metrics | Example Map, Acceptance Criteria, Open Questions | Clarified Story, Test Examples, Open Questions | Forecast Percentiles, Throughput Dataset, Risk Communication |
Tagsno overlap | FlowVisual managementDelivery | Behavior-Driven DevelopmentRequirementsExamplesRefinement | CollaborationBehavior-Driven DevelopmentQualityRefinement | ForecastingFlowDelivery |