View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Delivery Communication Plan |  Engineering Kanban |  Architecture Views and Beyond |  Architecture C4 Model |
|---|---|---|---|---|
Purposedifferent | When many people need to be informed in parallel and messages would otherwise arrive unevenly or too late, a Communication Plan orders communication reliably. Channels, audiences, and cadences interlock so important information doesn't get lost. | When work sits in too many parallel streams, throughput suffers and no one sees the bottlenecks. Kanban makes the flow of work visible and limits overload so a system becomes calmer and more predictable. | Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question. | 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 | Low | Medium | Medium | Low |
Timedifferent | 45-90 min | Ongoing | 1-3 Tage | 1-4 h |
Participantsdifferent | 2-6 | 2-12 | 1-4 | 1-5 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Communication Plan, Channel Matrix, Message Cadence | Kanban board, WIP policies, Flow metrics | Architecture Views, Cross-view Notes, Rationale | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | CommunicationStakeholdersDeliveryPlanning | FlowVisual managementDelivery | DocumentationStakeholdersArchitecture | ArchitectureCommunicationVisualization |