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 |  Growth Funnel Analysis |  Agile Acceptance Criteria Workshop |  Agile Example Mapping |
|---|---|---|---|---|
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 many visitors or users drop off along the way, the reason behind the number often stays hidden. Funnel Analysis exposes these transitions and makes visible exactly where the path collapses. | When a story needs clear checkpoints before implementation, it sharpens expectation and scope together. It sorts work by value, risk, and delivery ability. The result is captured as Acceptance Criteria and a Story Update. | 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 | Medium | Medium | Low | Low |
Timedifferent | 1-4 Wochen je Sprint, laufend | 1-3 h | 20-40 min pro Story | 30-60 min |
Participantsdifferent | 3-10 (Scrum Team) | 1-5 | 3-6 | 3-7 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Funnel report, Drop-off analysis, Optimization hypotheses | Acceptance Criteria, Story Update | Example Map, Acceptance Criteria, Open Questions |
Tagsno overlap | AgileIterationCadence | AnalyticsConversionGrowth | AgileRequirementsRefinementBehavior-Driven Development | Behavior-Driven DevelopmentRequirementsExamplesRefinement |