methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Paper illustration for Eat the Frog
Operations
Eat the Frog
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Purposedifferent
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.The method protects energy and attention for the task that creates the largest progress and is often postponed.The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design.An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable.
Complexitydifferent
LowLowMediumLow
Timedifferent
1-2 Tage15-90 min daily60-120 min15-45 min
Participantsdifferent
1-412-81-3
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncAsync
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewPriority Task, Completion Note, Daily FocusCommunication Canvas, Stakeholder Messages, Architecture Communication PlanADR File, Decision Log, Rationale
Tagsno overlap
ArchitectureDocumentationCommunication
PrioritizationProductivityFocusExecution
ArchitectureCommunicationStakeholdersCanvas
ArchitectureRationaleDocumentationGovernance
Add more methods