View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Product Discovery Context Canvas |  Agile Affinity Estimation |  Agile Planning Poker |  Agile Specification by Example |
|---|---|---|---|---|
Purposedifferent | 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 many tasks need to be classified quickly, it sorts them by perceived effort and similarity. It reduces the effort of fine-grained estimation for large volumes. | When estimates within the team diverge too much, it puts differing expectations on a common test bench. It separates rough complexity from unspoken assumptions. | 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. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 45-90 min | 30-90 min | 2-5 min je Item | 60-90 min pro Feature |
Participantsdifferent | 3-10 | 3-12 | 3-9 | 3-6 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Context canvas, Open questions, Shared context notes | Affinity Size Map, Grouped Estimates, Unclear Items | Relative Estimates, Assumption Notes, Split Candidates | Example Table, Acceptance Tests |
Tagsno overlap | ContextFramingRequirementsCanvas | EstimationBacklogRelative sizing | EstimationAgileRelative sizingTeam | AgileRequirementsExamplesBehavior-Driven Development |