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 Acceptance Criteria Workshop |  Innovation TRIZ |  Agile Example Mapping |  Innovation SCAMPER |
|---|---|---|---|---|
Purposedifferent | 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. | 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 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. | For an existing solution under pressure to change, the method deliberately opens space for systematic variants. It directs attention to rebuilding, combining, and repurposing rather than only new basic ideas. This produces concrete evolution paths for products, offerings, or workflows. |
Complexitydifferent | Low | High | Low | Low |
Timedifferent | 20-40 min pro Story | 1-4 h | 30-60 min | 30-60 min |
Participantsdifferent | 3-6 | 2-8 | 3-7 | 2-10 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Acceptance Criteria, Story Update | Contradiction Statement, Inventive Principles, Solution Concepts | Example Map, Acceptance Criteria, Open Questions | SCAMPER Idea List, Concept Shortlist, Variation Notes |
Tagsno overlap | AgileRequirementsRefinementBehavior-Driven Development | InnovationProblem solvingContradictionsCreativity | Behavior-Driven DevelopmentRequirementsExamplesRefinement | BrainstormingIdeationCreativityReframingInnovation |