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 Specification by Example | ![]() Delivery Value Stream Mapping | ![]() Agile Acceptance Criteria Workshop |
|---|---|---|---|
Purposedifferent | When business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests. | 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 a story needs clear checkpoints before implementation, it sharpens expectation and scope together. It sorts work by value, risk, and delivery ability. The result is captured as Acceptance Criteria and a Story Update. |
Complexitydifferent | Medium | Medium | Low |
Timedifferent | 60-90 min pro Feature | 1-3 h | 20-40 min pro Story |
Participantsdifferent | 3-6 | 4-10 | 3-6 |
Formatsame | Workshop | Workshop | Workshop |
Outputdifferent | Example Table, Acceptance Tests | Current-state map, Future-state map, Bottleneck list | Acceptance Criteria, Story Update |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | LeanFlowWasteDelivery | AgileRequirementsRefinementBehavior-Driven Development |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






