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 Scrum |  UX Design Lean UX Canvas |  Product Discovery Context Canvas |
|---|---|---|---|---|
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 team needs to work in a fixed delivery rhythm, it stabilizes cadence, responsibility, and feedback loops. It makes collaboration reliable across sprint boundaries. | The Lean UX Canvas helps clarify user behavior, touchpoints, and concept decisions. It makes assumptions and desired outcomes visible and captures the result as a completed canvas, hypothesis list, and first experiment. | 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. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 60-90 min pro Feature | 1-4 Wochen je Sprint, laufend | 2-3 h | 45-90 min |
Participantsdifferent | 3-6 | 3-10 (Scrum Team) | 3-8 | 3-10 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Example Table, Acceptance Tests | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Completed Lean UX Canvas, Hypothesis list, First experiment | Context canvas, Open questions, Shared context notes |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | AgileIterationCadence | CanvasHypothesisOutcomesDiscovery | ContextFramingRequirementsCanvas |