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 Affinity Estimation.
Agile
Affinity Estimation
Story Splitting method illustration showing its working structure
Agile
Story Splitting
Paper illustration for Monte Carlo Forecasting.
Delivery
Monte Carlo Forecasting
Paper illustration for Planning Poker.
Agile
Planning Poker
Purposedifferent
When many tasks need to be classified quickly, it sorts them by perceived effort and similarity. It reduces the effort of fine-grained estimation for large volumes.When a story becomes too large for a clean flow, it breaks scope down along value and risk. It shapes the work into a form that ships earlier and is easier to verify.Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as Forecast Percentiles, Throughput Dataset, and Risk Communication.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
MediumMediumHighLow
Timedifferent
30-90 min30-60 min30-90 min Setup, danach laufend2-5 min je Item
Participantsdifferent
3-122-61-83-9
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Affinity Size Map, Grouped Estimates, Unclear ItemsSmaller Stories, Acceptance Criteria, Split RationaleForecast Percentiles, Throughput Dataset, Risk CommunicationRelative Estimates, Assumption Notes, Split Candidates
Tagsno overlap
EstimationBacklogRelative sizing
BacklogIterationDelivery
ForecastingFlowDelivery
EstimationAgileRelative sizingTeam
Add more methods