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 RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration for Dot Estimation.
Facilitation
Dot Estimation
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
Purposedifferent
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.When size or effort can only be estimated roughly, Dot Estimation condenses the group's experience into a quick range. It turns individual contributions into a visible selection. The result is captured as an Effort Heatmap, Risk Signals, and Discussion Targets.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.
Complexitysame
LowLowLowLow
Timedifferent
30 min Setup, dann laufend5-20 min1-2 Tage15-45 min
Participantsdifferent
1-3 maintaining, briefing for everyone3-201-41-3
Formatdifferent
AsyncWorkshopWorkshop + asyncAsync
Outputdifferent
RAID Log, Status Report SourceEffort Heatmap, Risk Signals, Discussion TargetsArchitecture Document, Context View, Runtime View, Deployment ViewADR File, Decision Log, Rationale
Tagsno overlap
RiskTrackingStakeholdersGovernance
EstimationEffortRisk
ArchitectureDocumentationCommunication
ArchitectureRationaleDocumentationGovernance
Add more methods