View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Delivery Shape Up |  Agile Specification by Example |  Product Discovery Dual-Track Agile |  Agile Example Mapping |
|---|---|---|---|---|
Purposedifferent | Shape Up helps clarify scope, sequence, and delivery flow. It makes work boundaries and decisions explicit and captures results as pitches, bet-table decisions, and hill charts. | 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 uncertainty and delivery run in parallel, it separates learning work from implementation while keeping both connected. It prevents unvalidated ideas from falling directly into the delivery stream. | 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. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 6 Wochen Cycle + 2 Wochen Cool-Down | 60-90 min pro Feature | Laufend, Wochen bis Monate | 30-60 min |
Participantsdifferent | 2-4 pro Pitch | 3-6 | 4-10 | 3-7 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Pitches, Bet-table decisions, Hill charts, Cooldown outcomes | Example Table, Acceptance Tests | Discovery Backlog, Delivery Backlog, Experiment-Ergebnisse, Validierte Stories | Example Map, Acceptance Criteria, Open Questions |
Tagsno overlap | PlanningDeliveryAutonomy | AgileRequirementsExamplesBehavior-Driven Development | AgileDiscoveryDelivery | Behavior-Driven DevelopmentRequirementsExamplesRefinement |