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 of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration for Expectation Mapping.
Facilitation
Expectation Mapping
Paper board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
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.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 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 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.
Complexitydifferent
MediumLowLowLow
Timedifferent
30-90 min30 min Setup, dann laufend45-90 min20-40 min initial, dann laufend
Participantsdifferent
3-121-3 maintaining, briefing for everyone3-123-15
Formatdifferent
WorkshopAsyncWorkshopWorkshop + async
Outputdifferent
Affinity Size Map, Grouped Estimates, Unclear ItemsRAID Log, Status Report SourceExpectation Map, Alignment Notes, AgreementsROAM Board, Owner List
Tagsno overlap
EstimationBacklogRelative sizing
RiskTrackingStakeholdersGovernance
AlignmentStakeholdersTeam
RiskAgileTrackingAlignment
Add more methods