View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Delivery RAID Log |  Agile Example Mapping |  Product Discovery Context Canvas |  Agile Specification by Example |
|---|---|---|---|---|
Purposedifferent | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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. | 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 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 | Low | Low | Medium |
Timedifferent | 30 min Setup, dann laufend | 30-60 min | 45-90 min | 60-90 min pro Feature |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 3-7 | 3-10 | 3-6 |
Formatdifferent | Async | Workshop | Workshop | Workshop |
Outputdifferent | RAID Log, Status Report Source | Example Map, Acceptance Criteria, Open Questions | Context canvas, Open questions, Shared context notes | Example Table, Acceptance Tests |
Tagsno overlap | RiskTrackingStakeholdersGovernance | Behavior-Driven DevelopmentRequirementsExamplesRefinement | ContextFramingRequirementsCanvas | AgileRequirementsExamplesBehavior-Driven Development |