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 Three Amigos | ![]() Agile Acceptance Criteria Workshop | ![]() Architecture Architecture Communication Canvas | ![]() Architecture arc42 |
|---|---|---|---|---|
Purposedifferent | When story, test, and implementation could drift apart, it brings business perspective, engineering, and quality together early. It prevents a story from being read differently only late in the process. | 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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | 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. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 15-30 min | 20-40 min pro Story | 60-120 min | 1-2 Tage |
Participantsdifferent | 3 | 3-6 | 2-8 | 1-4 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Clarified Story, Test Examples, Open Questions | Acceptance Criteria, Story Update | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | CollaborationBehavior-Driven DevelopmentQualityRefinement | AgileRequirementsRefinementBehavior-Driven Development | ArchitectureCommunicationStakeholdersCanvas | ArchitectureDocumentationCommunication |



