View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Three AmigosARID (Active Reviews for Intermediate Designs)Architecture Decision RecordChatOps
| Criterion |  Agile Three Amigos |  Architecture ARID (Active Reviews for Intermediate Designs) |  Architecture Architecture Decision Record |  DevOps ChatOps |
|---|---|---|---|---|
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. | 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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | For operational work in a distributed team, the method links communication with direct system control. It records decisions right where the signal, the context, and the execution come together. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 15-30 min | 2–4 h review as a planning range; preparation and evaluation additional | 15-45 min | Ongoing |
Participantsdifferent | 3 | Designers, developers as users, and facilitation | 1-3 | 2-20 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + async |
Outputdifferent | Clarified Story, Test Examples, Open Questions | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | ADR File, Decision Log, Rationale | Chat Transcript, Action Log, Automations |
Tagsno overlap | CollaborationBehavior-Driven DevelopmentQualityRefinement | ArchitectureEngineeringFeedbackValidationTasks | ArchitectureRationaleDocumentationGovernance | CollaborationEngineeringIncident |