View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile Example Mapping |  Delivery Value Stream Mapping |  Engineering Kanban |  Agile Three Amigos |
|---|---|---|---|---|
Purposedifferent | 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 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 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 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. |
Complexitydifferent | Low | Medium | Medium | Low |
Timedifferent | 30-60 min | 1-3 h | Ongoing | 15-30 min |
Participantsdifferent | 3-7 | 4-10 | 2-12 | 3 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | Current-state map, Future-state map, Bottleneck list | Kanban board, WIP policies, Flow metrics | Clarified Story, Test Examples, Open Questions |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | LeanFlowWasteDelivery | FlowVisual managementDelivery | CollaborationBehavior-Driven DevelopmentQualityRefinement |