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 Dot Estimation.
Facilitation
Dot Estimation
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 PERT Estimation.
Decision Making
PERT Estimation
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 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.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.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.
Complexitydifferent
LowLowLowMedium
Timedifferent
1-2 Tage5-20 min15-45 min15-45 min
Participantsdifferent
1-43-201-31-8
Formatdifferent
Workshop + asyncWorkshopAsyncWorkshop + async
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewEffort Heatmap, Risk Signals, Discussion TargetsADR File, Decision Log, RationalePERT Estimate, Expected Value, Risk Notes
Tagsno overlap
ArchitectureDocumentationCommunication
EstimationEffortRisk
ArchitectureRationaleDocumentationGovernance
EstimationUncertaintyRisk
Add more methods