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 board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
Paper illustration for Dot Estimation.
Facilitation
Dot Estimation
Paper illustration for Planning Poker.
Agile
Planning Poker
Paper illustration for Expectation Mapping.
Facilitation
Expectation Mapping
Purposedifferent
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 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 estimates within the team diverge too much, it puts differing expectations on a common test bench. It separates rough complexity from unspoken assumptions.When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge.
Complexitysame
LowLowLowLow
Timedifferent
20-40 min initial, dann laufend5-20 min2-5 min je Item45-90 min
Participantsdifferent
3-153-203-93-12
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
ROAM Board, Owner ListEffort Heatmap, Risk Signals, Discussion TargetsRelative Estimates, Assumption Notes, Split CandidatesExpectation Map, Alignment Notes, Agreements
Tagsno overlap
RiskAgileTrackingAlignment
EstimationEffortRisk
EstimationAgileRelative sizingTeam
AlignmentStakeholdersTeam
Add more methods