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 of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
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 Affinity Estimation.
Agile
Affinity Estimation
Purposedifferent
Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting.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 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.
Complexitydifferent
LowLowLowMedium
Timedifferent
30 min Setup, dann laufend2-5 min je Item20-40 min initial, dann laufend30-90 min
Participantsdifferent
1-3 maintaining, briefing for everyone3-93-153-12
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
RAID Log, Status Report SourceRelative Estimates, Assumption Notes, Split CandidatesROAM Board, Owner ListAffinity Size Map, Grouped Estimates, Unclear Items
Tagsno overlap
RiskTrackingStakeholdersGovernance
EstimationAgileRelative sizingTeam
RiskAgileTrackingAlignment
EstimationBacklogRelative sizing
Add more methods