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 Working Agreements |  Agile Specification by Example |  Agile Example Mapping |
|---|---|---|---|---|
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 collaboration needs more than implicit expectations, it lays out shared ground rules openly. It creates reliability for conduct, availability, and decision paths. | 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. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 45-90 min | 45-90 min | 60-90 min pro Feature | 30-60 min |
Participantsdifferent | 3-10 | 3-12 | 3-6 | 3-7 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Context canvas, Open questions, Shared context notes | Working Agreements, Team Norms, Review Cadence | Example Table, Acceptance Tests | Example Map, Acceptance Criteria, Open Questions |
Tagsno overlap | ContextFramingRequirementsCanvas | TeamCollaborationAgile | AgileRequirementsExamplesBehavior-Driven Development | Behavior-Driven DevelopmentRequirementsExamplesRefinement |