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 TRIZ |
|---|---|---|---|
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 technical contradictions or trade-offs, the method looks for solutions that resolve opposing requirements at the same time. It translates limits into an explicit picture of conflict that becomes workable. This produces not just compromises but more elegant principles. |
Complexitydifferent | Low | Medium | High |
Timedifferent | 30-60 min | 60-90 min pro Feature | 1-4 h |
Participantsdifferent | 3-7 | 3-6 | 2-8 |
Formatdifferent | Workshop | Workshop | Workshop + async |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | Example Table, Acceptance Tests | Contradiction Statement, Inventive Principles, Solution Concepts |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | AgileRequirementsExamplesBehavior-Driven Development | InnovationProblem solvingContradictionsCreativity |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






