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 Sailboat Retrospective
Agile
Sailboat Retrospective
Paper illustration of Strategy Execution Loop with its method-specific working model.
Business Strategy
Strategy Execution Loop
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.When a team wants to read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture.The Strategy Execution Loop helps avoid treating strategy as a one-off document. It makes visible how strategic decisions are turned into objectives, initiatives, operational work, measurement, and learning.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
LowLowHighLow
Timedifferent
1-2 Tage45-90 minInitial 3-6 h, then monthly or quarterly reviews15-45 min
Participantsdifferent
1-44-125-121-3
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncAsync
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewSailboat Board, Risks, Improvement ActionsExecution Loop, Review Cadence, Strategic Learning LogADR File, Decision Log, Rationale
Tagsno overlap
ArchitectureDocumentationCommunication
RetrospectiveTeamImprovement
ExecutionCadenceLearningGovernance
ArchitectureRationaleDocumentationGovernance
Add more methods