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 Architecture Communication Canvas |  Architecture C4 Model |
|---|---|---|---|
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 Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | 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. |
Complexitydifferent | Medium | Medium | Low |
Timedifferent | 30-60 min | 60-120 min | 1-4 h |
Participantsdifferent | 2-6 | 2-8 | 1-5 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Smaller Stories, Acceptance Criteria, Split Rationale | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | BacklogIterationDelivery | ArchitectureCommunicationStakeholdersCanvas | ArchitectureCommunicationVisualization |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
