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 Specification by Example |  Agile Bucket System |  Agile Ideal Days |  Agile Planning Poker |
|---|---|---|---|---|
Purposedifferent | When business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests. | 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. | 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 estimates within the team diverge too much, it puts differing expectations on a common test bench. It separates rough complexity from unspoken assumptions. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 60-90 min pro Feature | 30-90 min | 15-60 min | 2-5 min je Item |
Participantsdifferent | 3-6 | 3-12 | 2-9 | 3-9 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Example Table, Acceptance Tests | Bucketed Backlog, Relative Estimates, Split Candidates | Ideal Day Estimates, Assumption Notes, Capacity Caveats | Relative Estimates, Assumption Notes, Split Candidates |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | EstimationBacklogRelative sizing | EstimationEffortAgile | EstimationAgileRelative sizingTeam |