View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Innovation SCAMPER | ![]() Agile Acceptance Criteria Workshop | ![]() Innovation Reverse Brainstorming | ![]() Agile Example Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | 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 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. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 30-60 min | 20-40 min pro Story | 30-60 min | 30-60 min |
Participantsdifferent | 2-10 | 3-6 | 3-12 | 3-7 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | SCAMPER Idea List, Concept Shortlist, Variation Notes | Acceptance Criteria, Story Update | Reverse Ideas, Risk Themes, Solution Ideas | Example Map, Acceptance Criteria, Open Questions |
Tagsno overlap | BrainstormingIdeationCreativityReframingInnovation | AgileRequirementsRefinementBehavior-Driven Development | BrainstormingIdeationCreativityRisk | Behavior-Driven DevelopmentRequirementsExamplesRefinement |



