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 Specification by Example |  Agile Example Mapping |  Product Strategy RICE Scoring |  Agile T-Shirt Sizing |
|---|---|---|---|---|
Purposedifferent | 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. | When many initiatives compete for the same resources, it brings reach, impact, confidence, and effort into one shared ranking. It makes prioritization economically connectable. | When effort only needs to be classified roughly, it makes comparability more important than false precision. It helps sort work quickly into manageable sizes. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 60-90 min pro Feature | 30-60 min | 60-90 min | 15-45 min |
Participantsdifferent | 3-6 | 3-7 | 2-10 | 2-12 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Example Table, Acceptance Tests | Example Map, Acceptance Criteria, Open Questions | RICE Scores, Ranked List, Assumption Log | Size Buckets, Rough Backlog Map, Split Candidates |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | Behavior-Driven DevelopmentRequirementsExamplesRefinement | PrioritizationScoringRoadmapTradeoffs | EstimationAgileRoadmap |