View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture C4 Model |  Product Discovery Dual-Track Agile |  Agile Acceptance Criteria Workshop |
|---|---|---|---|
Purposedifferent | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | 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. | 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. |
Complexitydifferent | Low | Medium | Low |
Timedifferent | 1-4 h | Laufend, Wochen bis Monate | 20-40 min pro Story |
Participantsdifferent | 1-5 | 4-10 | 3-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | Discovery Backlog, Delivery Backlog, Experiment-Ergebnisse, Validierte Stories | Acceptance Criteria, Story Update |
Tagsno overlap | ArchitectureCommunicationVisualization | AgileDiscoveryDelivery | AgileRequirementsRefinementBehavior-Driven Development |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
