View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Specification by ExampleARID (Active Reviews for Intermediate Designs)Architecture Communication Canvas
| Criterion | ![]() Agile Specification by Example | ![]() Architecture ARID (Active Reviews for Intermediate Designs) | ![]() Architecture Architecture Communication Canvas |
|---|---|---|---|
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. | ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 60-90 min pro Feature | 2–4 h review as a planning range; preparation and evaluation additional | 60-120 min |
Participantsdifferent | 3-6 | Designers, developers as users, and facilitation | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Example Table, Acceptance Tests | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | ArchitectureEngineeringFeedbackValidationTasks | ArchitectureCommunicationStakeholdersCanvas |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






