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 |  Architecture Architecture Inception Canvas |  Architecture Software Architecture 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. | 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. | The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 1-4 Wochen je Sprint, laufend | 60-90 min pro Feature | 1-2 h | 1-2 h |
Participantsdifferent | 3-10 (Scrum Team) | 3-6 | 3-8 | 3-10 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Example Table, Acceptance Tests | Inception Canvas, Risks, Goal List, Open Questions | Architecture Canvas, Goals, Constraints, Quality Attributes |
Tagsno overlap | AgileIterationCadence | AgileRequirementsExamplesBehavior-Driven Development | AlignmentArchitectureCanvas | CanvasArchitectureAlignmentWorkshop |