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
Stakeholder Mapping
Facilitation
Stakeholder 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 an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first.
Complexitysame
LowLowLow
Timedifferent
2-5 min je Item20-40 min initial, dann laufend60–90 min
Participantsdifferent
3-93-152-8
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Relative Estimates, Assumption Notes, Split CandidatesROAM Board, Owner ListStakeholder Map, Engagement Plan, Risk Notes
Tagsno overlap
EstimationAgileRelative sizingTeam
RiskAgileTrackingAlignment
StakeholdersAlignmentFacilitationChange
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
Paper illustration for Expectation Mapping.
Facilitation
Expectation Mapping
Paper illustration of Power-Interest Grid with a method-specific labelled workspace.
Facilitation
Power Interest Grid