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 Sprint Retrospective |  Operations Process Mapping |  Architecture Architecture Communication Canvas |  Architecture arc42 |
|---|---|---|---|---|
Purposedifferent | When a sprint is over and friction shouldn't simply be carried forward, it opens the view onto collaboration and patterns. It creates space to see causes and changes together. | With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | 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 | Low | Medium | Medium | Low |
Timedifferent | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 1-3 h | 60-120 min | 1-2 Tage |
Participantsdifferent | Scrum Team | 3-10 | 2-8 | 1-4 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Improvement actions, Team agreements | Process Map, Handoff List, Improvement Backlog | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | RetrospectiveImprovementLearning | ProcessOperationsImprovement | ArchitectureCommunicationStakeholdersCanvas | ArchitectureDocumentationCommunication |