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 Bucket System.
Agile
Bucket System
Paper board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
Paper illustration for Planning Poker.
Agile
Planning Poker
Paper illustration for Dot Estimation.
Facilitation
Dot Estimation
Purposedifferent
When a large batch of work needs a fast, rough estimate, it sorts items into predefined size buckets. It sorts work by value, risk, and delivery ability. The result is captured as a Bucketed Backlog, Relative Estimates, and Split Candidates.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.When estimates within the team diverge too much, it puts differing expectations on a common test bench. It separates rough complexity from unspoken assumptions.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.
Complexitydifferent
MediumLowLowLow
Timedifferent
30-90 min20-40 min initial, dann laufend2-5 min je Item5-20 min
Participantsdifferent
3-123-153-93-20
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Bucketed Backlog, Relative Estimates, Split CandidatesROAM Board, Owner ListRelative Estimates, Assumption Notes, Split CandidatesEffort Heatmap, Risk Signals, Discussion Targets
Tagsno overlap
EstimationBacklogRelative sizing
RiskAgileTrackingAlignment
EstimationAgileRelative sizingTeam
EstimationEffortRisk
Add more methods