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 Three Amigos |  Innovation TRIZ |  Agile Specification by Example |  Agile Example Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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 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 | Low | High | Medium | Low |
Timedifferent | 15-30 min | 1-4 h | 60-90 min pro Feature | 30-60 min |
Participantsdifferent | 3 | 2-8 | 3-6 | 3-7 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Clarified Story, Test Examples, Open Questions | Contradiction Statement, Inventive Principles, Solution Concepts | Example Table, Acceptance Tests | Example Map, Acceptance Criteria, Open Questions |
Tagsno overlap | CollaborationBehavior-Driven DevelopmentQualityRefinement | InnovationProblem solvingContradictionsCreativity | AgileRequirementsExamplesBehavior-Driven Development | Behavior-Driven DevelopmentRequirementsExamplesRefinement |