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
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Paper illustration for PERT Estimation.
Decision Making
PERT Estimation
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Purposedifferent
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.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.On complex initiatives, a plain average tends to understate just how uncertain the outcome really is. It separates options, evaluation criteria, and open risks. The result is captured as a PERT Estimate, Expected Value, and Risk Notes.Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting.
Complexitydifferent
LowLowMediumLow
Timedifferent
15-45 min1-2 Tage15-45 min30 min Setup, dann laufend
Participantsdifferent
1-31-41-81-3 maintaining, briefing for everyone
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
ADR File, Decision Log, RationaleArchitecture Document, Context View, Runtime View, Deployment ViewPERT Estimate, Expected Value, Risk NotesRAID Log, Status Report Source
Tagsno overlap
ArchitectureRationaleDocumentationGovernance
ArchitectureDocumentationCommunication
EstimationUncertaintyRisk
RiskTrackingStakeholdersGovernance
Add more methods