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 NoEstimates.
Agile
NoEstimates
Paper illustration for Wideband Delphi.
Decision Making
Wideband Delphi
Paper illustration for Knowledge Mapping.
Knowledge Modeling
Knowledge Mapping
Paper illustration of a Concept Map with concepts and labelled links
Knowledge Modeling
Concept Mapping
Purposedifferent
When estimating slows a team down more than it helps, it shifts the focus to flow, small slices, and real lead time. It sorts work by value, risk, and delivery ability. The result is captured as Throughput Data, Flow Forecast, and Slicing Rules.A single opinion rarely holds up for planning when the future is genuinely uncertain. It separates options, evaluation criteria, and open risks. The result is captured as an Estimate Range, Assumption Log, and Expert Consensus Notes.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.Concept Mapping arranges terms and relationships in a network that makes subject-matter connections tangible. It fits when a topic needs to be understood structurally rather than linearly.
Complexitydifferent
MediumHighMediumMedium
Timedifferent
laufend1-4 h or multiple rounds1-3 h1-2 h
Participantsdifferent
2-124-12 Experten3-121-8
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Throughput Data, Flow Forecast, Slicing RulesEstimate Range, Assumption Log, Expert Consensus NotesKnowledge Map, Critical Knowledge Areas, Transfer PlanConcept Map, Relationship Labels, Knowledge Gaps
Tagsno overlap
EstimationForecastingFlow
EstimationExpertsForecasting
KnowledgeMappingRisk
KnowledgeConceptsMappingSensemaking
Add more methods