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 of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Paper illustration for Monte Carlo Forecasting.
Delivery
Monte Carlo Forecasting
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
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.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.Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as Forecast Percentiles, Throughput Dataset, and Risk Communication.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.
Complexitydifferent
LowLowHighLow
Timedifferent
5-20 min15-45 min30-90 min Setup, danach laufend1-2 Tage
Participantsdifferent
3-201-31-81-4
Formatdifferent
WorkshopAsyncWorkshop + asyncWorkshop + async
Outputdifferent
Effort Heatmap, Risk Signals, Discussion TargetsADR File, Decision Log, RationaleForecast Percentiles, Throughput Dataset, Risk CommunicationArchitecture Document, Context View, Runtime View, Deployment View
Tagsno overlap
EstimationEffortRisk
ArchitectureRationaleDocumentationGovernance
ForecastingFlowDelivery
ArchitectureDocumentationCommunication
Add more methods