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 Scrum | ![]() Agile Example Mapping | ![]() UX Design Lean UX Canvas | ![]() Product Discovery Context Canvas |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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 | Low | Medium | Low |
Timedifferent | 1-4 Wochen je Sprint, laufend | 30-60 min | 2-3 h | 45-90 min |
Participantsdifferent | 3-10 (Scrum Team) | 3-7 | 3-8 | 3-10 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Example Map, Acceptance Criteria, Open Questions | Completed Lean UX Canvas, Hypothesis list, First experiment | Context canvas, Open questions, Shared context notes |
Tagsno overlap | AgileIterationCadence | Behavior-Driven DevelopmentRequirementsExamplesRefinement | CanvasHypothesisOutcomesDiscovery | ContextFramingRequirementsCanvas |



