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 of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Paper illustration for Team Charter.
Facilitation
Team Charter
Architecture Inception Canvas method illustration showing its working structure
Architecture
Architecture Inception Canvas
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.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.When a team is starting fresh or working past each other, Team Charter clarifies the shared working basis. It visibly sets out how collaboration, decision paths, and mutual conduct should work day to day.The Architecture Inception Canvas bundles the first architecture questions into a compact decision picture. It fits when an initiative is still in motion but still needs clear guardrails.
Complexitydifferent
LowLowMediumLow
Timedifferent
1-2 Tage15-45 min2-4 h1-2 h
Participantsdifferent
1-41-33-123-8
Formatdifferent
Workshop + asyncAsyncWorkshopWorkshop
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewADR File, Decision Log, RationaleTeam Charter, Working Norms, Role NotesInception Canvas, Risks, Goal List, Open Questions
Tagsno overlap
ArchitectureDocumentationCommunication
ArchitectureRationaleDocumentationGovernance
TeamAlignmentCollaboration
AlignmentArchitectureCanvas
Add more methods