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 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
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
Purposedifferent
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.When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable.
Complexitydifferent
LowLowLowMedium
Timedifferent
2-5 min je Item20-40 min initial, dann laufend45-90 min1-2 h
Participantsdifferent
3-93-153-124-12
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Relative Estimates, Assumption Notes, Split CandidatesROAM Board, Owner ListExpectation Map, Alignment Notes, AgreementsAlignment Map, Open Issues, Decision Questions
Tagsno overlap
EstimationAgileRelative sizingTeam
RiskAgileTrackingAlignment
AlignmentStakeholdersTeam
AlignmentStakeholdersStrategyFacilitation
Add more methods