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 Story Points.
Agile
Story Points
Paper illustration for Expectation Mapping.
Facilitation
Expectation Mapping
Paper board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
Paper illustration for Dot Estimation.
Facilitation
Dot Estimation
Purposedifferent
When teams want to rate complexity rather than hours, it creates a shared, relative scale. It sorts work by value, risk, and delivery ability. The result is captured as Point Estimates, Reference Stories, and Velocity Data.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.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.
Complexitydifferent
MediumLowLowLow
Timedifferent
laufend, 1-5 min je Item45-90 min20-40 min initial, dann laufend5-20 min
Participantsdifferent
3-93-123-153-20
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
Point Estimates, Reference Stories, Velocity DataExpectation Map, Alignment Notes, AgreementsROAM Board, Owner ListEffort Heatmap, Risk Signals, Discussion Targets
Tagsno overlap
EstimationAgileMeasurement
AlignmentStakeholdersTeam
RiskAgileTrackingAlignment
EstimationEffortRisk
Add more methods