View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Product Discovery Context Canvas |  Architecture arc42 |  Agile Acceptance Criteria Workshop |  Agile Specification by Example |
|---|---|---|---|---|
Purposedifferent | 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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | 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 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 | 45-90 min | 1-2 Tage | 20-40 min pro Story | 60-90 min pro Feature |
Participantsdifferent | 3-10 | 1-4 | 3-6 | 3-6 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Context canvas, Open questions, Shared context notes | Architecture Document, Context View, Runtime View, Deployment View | Acceptance Criteria, Story Update | Example Table, Acceptance Tests |
Tagsno overlap | ContextFramingRequirementsCanvas | ArchitectureDocumentationCommunication | AgileRequirementsRefinementBehavior-Driven Development | AgileRequirementsExamplesBehavior-Driven Development |