View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile Ideal Days |  Agile Acceptance Criteria Workshop |  Agile Planning Poker |  Agile Example Mapping |
|---|---|---|---|---|
Purposedifferent | When effort needs to be thought of as real working time, it offers a simple common denominator for comparison. It sorts work by value, risk, and delivery ability. The result is captured as Ideal Day Estimates, Assumption Notes, and Capacity Caveats. | When a story needs clear checkpoints before implementation, it sharpens expectation and scope together. It sorts work by value, risk, and delivery ability. The result is captured as Acceptance Criteria and a Story Update. | 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 story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 15-60 min | 20-40 min pro Story | 2-5 min je Item | 30-60 min |
Participantsdifferent | 2-9 | 3-6 | 3-9 | 3-7 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Ideal Day Estimates, Assumption Notes, Capacity Caveats | Acceptance Criteria, Story Update | Relative Estimates, Assumption Notes, Split Candidates | Example Map, Acceptance Criteria, Open Questions |
Tagsno overlap | EstimationEffortAgile | AgileRequirementsRefinementBehavior-Driven Development | EstimationAgileRelative sizingTeam | Behavior-Driven DevelopmentRequirementsExamplesRefinement |