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 |  Delivery RAID Log |  Architecture Architecture Decision Record |  Agile Acceptance Criteria Workshop |
|---|---|---|---|---|
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. | 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. | 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. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 15-30 min | 30 min Setup, dann laufend | 15-45 min | 20-40 min pro Story |
Participantsdifferent | 3 | 1-3 maintaining, briefing for everyone | 1-3 | 3-6 |
Formatdifferent | Workshop + async | Async | Async | Workshop |
Outputdifferent | Clarified Story, Test Examples, Open Questions | RAID Log, Status Report Source | ADR File, Decision Log, Rationale | Acceptance Criteria, Story Update |
Tagsno overlap | CollaborationBehavior-Driven DevelopmentQualityRefinement | RiskTrackingStakeholdersGovernance | ArchitectureRationaleDocumentationGovernance | AgileRequirementsRefinementBehavior-Driven Development |