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 |  Product Discovery Context Canvas |  Agile Planning Poker |
|---|---|---|---|
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 an environment of users, systems, and constraints is hard to grasp, it puts the context compactly on the table. It creates a clear reading of influence, boundary, and dependency. | When estimates within the team diverge too much, it puts differing expectations on a common test bench. It separates rough complexity from unspoken assumptions. |
Complexitydifferent | Medium | Low | Low |
Timedifferent | 60-90 min pro Feature | 45-90 min | 2-5 min je Item |
Participantsdifferent | 3-6 | 3-10 | 3-9 |
Formatdifferent | Workshop | Workshop | Workshop + async |
Outputdifferent | Example Table, Acceptance Tests | Context canvas, Open questions, Shared context notes | Relative Estimates, Assumption Notes, Split Candidates |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | ContextFramingRequirementsCanvas | EstimationAgileRelative sizingTeam |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
