View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Engineering Kanban |  Architecture Architecture Communication Canvas |  Architecture Software Architecture Canvas |  Delivery Communication Plan |
|---|---|---|---|---|
Purposedifferent | 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. | 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 Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly. | 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. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | Ongoing | 60-120 min | 1-2 h | 45-90 min |
Participantsdifferent | 2-12 | 2-8 | 3-10 | 2-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Kanban board, WIP policies, Flow metrics | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Architecture Canvas, Goals, Constraints, Quality Attributes | Communication Plan, Channel Matrix, Message Cadence |
Tagsno overlap | FlowVisual managementDelivery | ArchitectureCommunicationStakeholdersCanvas | CanvasArchitectureAlignmentWorkshop | CommunicationStakeholdersDeliveryPlanning |