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 |  Agile Specification by Example |  Innovation Reverse Brainstorming |
|---|---|---|---|
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 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. | For persistent errors or blockages, the method shifts the view to the opposite of the desired effect. It exposes the mechanics of failure and makes hidden causes easier to grasp. This makes improvement more concrete and the problem clearer. |
Complexitydifferent | Low | Medium | Low |
Timedifferent | 30-60 min | 60-90 min pro Feature | 30-60 min |
Participantsdifferent | 3-7 | 3-6 | 3-12 |
Formatsame | Workshop | Workshop | Workshop |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | Example Table, Acceptance Tests | Reverse Ideas, Risk Themes, Solution Ideas |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | AgileRequirementsExamplesBehavior-Driven Development | BrainstormingIdeationCreativityRisk |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
