View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Product Discovery Dual-Track Agile |  Architecture Architecture Decision Record |  Agile Acceptance Criteria Workshop |  Architecture arc42 |
|---|---|---|---|---|
Purposedifferent | When uncertainty and delivery run in parallel, it separates learning work from implementation while keeping both connected. It prevents unvalidated ideas from falling directly into the delivery stream. | 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. | 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 | Medium | Low | Low | Low |
Timedifferent | Laufend, Wochen bis Monate | 15-45 min | 20-40 min pro Story | 1-2 Tage |
Participantsdifferent | 4-10 | 1-3 | 3-6 | 1-4 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop + async |
Outputdifferent | Discovery Backlog, Delivery Backlog, Experiment-Ergebnisse, Validierte Stories | ADR File, Decision Log, Rationale | Acceptance Criteria, Story Update | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | AgileDiscoveryDelivery | ArchitectureRationaleDocumentationGovernance | AgileRequirementsRefinementBehavior-Driven Development | ArchitectureDocumentationCommunication |