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 Specification by Example |  Delivery RAID Log |  Architecture Architecture Communication Canvas |  Agile Example Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | 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 | Low | Medium | Low |
Timedifferent | 60-90 min pro Feature | 30 min Setup, dann laufend | 60-120 min | 30-60 min |
Participantsdifferent | 3-6 | 1-3 maintaining, briefing for everyone | 2-8 | 3-7 |
Formatdifferent | Workshop | Async | Workshop + async | Workshop |
Outputdifferent | Example Table, Acceptance Tests | RAID Log, Status Report Source | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Example Map, Acceptance Criteria, Open Questions |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | RiskTrackingStakeholdersGovernance | ArchitectureCommunicationStakeholdersCanvas | Behavior-Driven DevelopmentRequirementsExamplesRefinement |