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 Affinity Estimation.
Agile
Affinity Estimation
Paper illustration for Planning Poker.
Agile
Planning Poker
Paper board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
Paper illustration for Expectation Mapping.
Facilitation
Expectation Mapping
Purposedifferent
When many tasks need to be classified quickly, it sorts them by perceived effort and similarity. It reduces the effort of fine-grained estimation for large volumes.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 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 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.
Complexitydifferent
MediumLowLowLow
Timedifferent
30-90 min2-5 min je Item20-40 min initial, dann laufend45-90 min
Participantsdifferent
3-123-93-153-12
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Affinity Size Map, Grouped Estimates, Unclear ItemsRelative Estimates, Assumption Notes, Split CandidatesROAM Board, Owner ListExpectation Map, Alignment Notes, Agreements
Tagsno overlap
EstimationBacklogRelative sizing
EstimationAgileRelative sizingTeam
RiskAgileTrackingAlignment
AlignmentStakeholdersTeam
Add more methods