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 illustration for Ideal Days.
Agile
Ideal Days
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 estimates within the team diverge too much, it puts differing expectations on a common test bench. It separates rough complexity from unspoken assumptions.When effort needs to be thought of as real working time, it offers a simple common denominator for comparison. It sorts work by value, risk, and delivery ability. The result is captured as Ideal Day Estimates, Assumption Notes, and Capacity Caveats.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.
Complexitysame
LowLowLowLow
Timedifferent
2-5 min je Item15-60 min20-40 min initial, dann laufend45-90 min
Participantsdifferent
3-92-93-153-12
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Relative Estimates, Assumption Notes, Split CandidatesIdeal Day Estimates, Assumption Notes, Capacity CaveatsROAM Board, Owner ListExpectation Map, Alignment Notes, Agreements
Tagsno overlap
EstimationAgileRelative sizingTeam
EstimationEffortAgile
RiskAgileTrackingAlignment
AlignmentStakeholdersTeam
Add more methods