View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Engineering Failure Scenario Analysis |  Decision Making Three-Point Estimation |  Agile Planning Poker |  Agile Affinity Estimation |
|---|---|---|---|---|
Purposedifferent | In critical processes, it is not enough to plan only for the normal case. Failure Scenario Analysis looks at the path into failure and shows which failures, chains, and control gaps cause the most damage. | A single estimate for effort, time, or risk often looks too smooth for the real uncertainty behind it. It separates options, evaluation criteria, and open risks. The result is captured as a Three-Point Estimate, Risk Range, and Assumption 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. | 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. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 1-3 h | 10-30 min je Item | 2-5 min je Item | 30-90 min |
Participantsdifferent | 3-8 | 1-8 | 3-9 | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | Three-Point Estimate, Risk Range, Assumption Notes | Relative Estimates, Assumption Notes, Split Candidates | Affinity Size Map, Grouped Estimates, Unclear Items |
Tagsno overlap | FailureResilienceRisk | EstimationUncertaintyForecasting | EstimationAgileRelative sizingTeam | EstimationBacklogRelative sizing |