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 Planning Poker.
Agile
Planning Poker
Paper illustration for Bucket System.
Agile
Bucket System
A hypothetical failure makes concrete risks, signals, and fitting mitigations visible.
Decision Making
Pre-Mortem
Paper illustration for Constraint Analysis.
Decision Making
Constraint Analysis
Purposedifferent
When estimates within the team diverge too much, it puts differing expectations on a common test bench. It separates rough complexity from unspoken assumptions.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.In early initiatives with many uncertainties, planning quickly turns too optimistic. A pre-mortem makes the expected failure visible in advance and sharpens the view of causes, gaps, and countermeasures.When an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped.
Complexitydifferent
LowMediumLowLow
Timedifferent
2-5 min je Item30-90 min20–45 min30-90 min
Participantsdifferent
3-93-12Small cross-functional group2-8
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop + async
Outputdifferent
Relative Estimates, Assumption Notes, Split CandidatesBucketed Backlog, Relative Estimates, Split CandidatesRisk list, Mitigation plan, Assumption logConstraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries
Tagsno overlap
EstimationAgileRelative sizingTeam
EstimationBacklogRelative sizing
RiskDecisionFailurePlanning
ConstraintsDecisionPlanningOptions
Add more methods