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 for Dot Estimation.
Facilitation
Dot Estimation
Paper illustration for Ideal Days.
Agile
Ideal Days
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
Purposedifferent
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.When effort needs to be thought of as real working time, it offers a simple common denominator for comparison. It sorts work by value, risk, and delivery ability. The result is captured as Ideal Day Estimates, Assumption Notes, and Capacity Caveats.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.
Complexitydifferent
LowLowLowMedium
Timedifferent
5-20 min15-60 min1-2 Tage15-45 min
Participantsdifferent
3-202-91-41-8
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Effort Heatmap, Risk Signals, Discussion TargetsIdeal Day Estimates, Assumption Notes, Capacity CaveatsArchitecture Document, Context View, Runtime View, Deployment ViewPERT Estimate, Expected Value, Risk Notes
Tagsno overlap
EstimationEffortRisk
EstimationEffortAgile
ArchitectureDocumentationCommunication
EstimationUncertaintyRisk
Add more methods