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 Expectation Mapping.
Facilitation
Expectation Mapping
Paper illustration for Bucket System.
Agile
Bucket System
Paper board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
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 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 a large batch of work needs a fast, rough estimate, it sorts items into predefined size buckets. It sorts work by value, risk, and delivery ability. The result is captured as a Bucketed Backlog, Relative Estimates, and Split Candidates.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
LowLowMediumLow
Timedifferent
30 min Setup, dann laufend45-90 min30-90 min20-40 min initial, dann laufend
Participantsdifferent
1-3 maintaining, briefing for everyone3-123-123-15
Formatdifferent
AsyncWorkshopWorkshopWorkshop + async
Outputdifferent
RAID Log, Status Report SourceExpectation Map, Alignment Notes, AgreementsBucketed Backlog, Relative Estimates, Split CandidatesROAM Board, Owner List
Tagsno overlap
RiskTrackingStakeholdersGovernance
AlignmentStakeholdersTeam
EstimationBacklogRelative sizing
RiskAgileTrackingAlignment
Add more methods