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 Story Splitting |  Architecture C4 Model |  Delivery Shape Up |  Architecture arc42 |
|---|---|---|---|---|
Purposedifferent | When a story becomes too large for a clean flow, it breaks scope down along value and risk. It shapes the work into a form that ships earlier and is easier to verify. | 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. | Shape Up helps clarify scope, sequence, and delivery flow. It makes work boundaries and decisions explicit and captures results as pitches, bet-table decisions, and hill charts. | 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 | Medium | Low |
Timedifferent | 30-60 min | 1-4 h | 6 Wochen Cycle + 2 Wochen Cool-Down | 1-2 Tage |
Participantsdifferent | 2-6 | 1-5 | 2-4 pro Pitch | 1-4 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Smaller Stories, Acceptance Criteria, Split Rationale | Context Diagram, Container Diagram, Component Diagram | Pitches, Bet-table decisions, Hill charts, Cooldown outcomes | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | BacklogIterationDelivery | ArchitectureCommunicationVisualization | PlanningDeliveryAutonomy | ArchitectureDocumentationCommunication |