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 Dot Estimation.
Facilitation
Dot Estimation
Paper illustration of Team API with its method-specific working model.
Team Design
Team API
Paper board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
Paper illustration for PERT Estimation.
Decision Making
PERT Estimation
Purposedifferent
When size or effort can only be estimated roughly, Dot Estimation condenses the group's experience into a quick range. It turns individual contributions into a visible selection. The result is captured as an Effort Heatmap, Risk Signals, and Discussion Targets.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.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.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.
Complexitydifferent
LowLowLowMedium
Timedifferent
5-20 minHalf day initial, dann laufend20-40 min initial, dann laufend15-45 min
Participantsdifferent
3-20Ein Team plus Stakeholder3-151-8
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Effort Heatmap, Risk Signals, Discussion TargetsTeam API DocumentROAM Board, Owner ListPERT Estimate, Expected Value, Risk Notes
Tagsno overlap
EstimationEffortRisk
TeamAlignmentCommunicationService
RiskAgileTrackingAlignment
EstimationUncertaintyRisk
Add more methods