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 PERT Estimation.
Decision Making
PERT Estimation
Paper illustration for Planning Poker.
Agile
Planning Poker
Paper illustration for Knowledge Mapping.
Knowledge Modeling
Knowledge Mapping
Paper illustration for Dot Estimation.
Facilitation
Dot Estimation
Purposedifferent
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.Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable.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.
Complexitydifferent
MediumLowMediumLow
Timedifferent
15-45 min2-5 min je Item1-3 h5-20 min
Participantsdifferent
1-83-93-123-20
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
PERT Estimate, Expected Value, Risk NotesRelative Estimates, Assumption Notes, Split CandidatesKnowledge Map, Critical Knowledge Areas, Transfer PlanEffort Heatmap, Risk Signals, Discussion Targets
Tagsno overlap
EstimationUncertaintyRisk
EstimationAgileRelative sizingTeam
KnowledgeMappingRisk
EstimationEffortRisk
Add more methods