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 Specification by Example |  Product Discovery Context Canvas |  Architecture Architecture Inception 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 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 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. | The Architecture Inception Canvas bundles the first architecture questions into a compact decision picture. It fits when an initiative is still in motion but still needs clear guardrails. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 1-4 Wochen je Sprint, laufend | 60-90 min pro Feature | 45-90 min | 1-2 h |
Participantsdifferent | 3-10 (Scrum Team) | 3-6 | 3-10 | 3-8 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Example Table, Acceptance Tests | Context canvas, Open questions, Shared context notes | Inception Canvas, Risks, Goal List, Open Questions |
Tagsno overlap | AgileIterationCadence | AgileRequirementsExamplesBehavior-Driven Development | ContextFramingRequirementsCanvas | AlignmentArchitectureCanvas |