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 RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration for NoEstimates.
Agile
NoEstimates
Paper board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
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.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 estimating slows a team down more than it helps, it shifts the focus to flow, small slices, and real lead time. It sorts work by value, risk, and delivery ability. The result is captured as Throughput Data, Flow Forecast, and Slicing Rules.When work needs to move between different states or columns, it makes that movement and its handoffs legible. It sorts work by value, risk, and delivery ability. The result is captured as a ROAM Board and an Owner List.
Complexitydifferent
LowLowMediumLow
Timedifferent
5-20 min30 min Setup, dann laufendlaufend20-40 min initial, dann laufend
Participantsdifferent
3-201-3 maintaining, briefing for everyone2-123-15
Formatdifferent
WorkshopAsyncWorkshop + asyncWorkshop + async
Outputdifferent
Effort Heatmap, Risk Signals, Discussion TargetsRAID Log, Status Report SourceThroughput Data, Flow Forecast, Slicing RulesROAM Board, Owner List
Tagsno overlap
EstimationEffortRisk
RiskTrackingStakeholdersGovernance
EstimationForecastingFlow
RiskAgileTrackingAlignment
Add more methods