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 board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
Paper illustration of Team API with its method-specific working model.
Team Design
Team API
Paper illustration for PERT Estimation.
Decision Making
PERT Estimation
Paper illustration for Planning Poker.
Agile
Planning Poker
Purposedifferent
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 expectations between teams stay fuzzy, it describes how a team can be reached, used, and held accountable. It clarifies responsibility, interaction, and load between teams. The result is captured as a Team API document.On complex initiatives, a plain average tends to understate just how uncertain the outcome really is. It separates options, evaluation criteria, and open risks. The result is captured as a PERT Estimate, Expected Value, and Risk Notes.When estimates within the team diverge too much, it puts differing expectations on a common test bench. It separates rough complexity from unspoken assumptions.
Complexitydifferent
LowLowMediumLow
Timedifferent
20-40 min initial, dann laufendHalf day initial, dann laufend15-45 min2-5 min je Item
Participantsdifferent
3-15Ein Team plus Stakeholder1-83-9
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
ROAM Board, Owner ListTeam API DocumentPERT Estimate, Expected Value, Risk NotesRelative Estimates, Assumption Notes, Split Candidates
Tagsno overlap
RiskAgileTrackingAlignment
TeamAlignmentCommunicationService
EstimationUncertaintyRisk
EstimationAgileRelative sizingTeam
Add more methods