Relative Estimation (Agile Estimation) Experiment

Experiment: relative estimation

Problem: Humans are not good at estimating time and cost but they are excellent at comparing items, yet we need to be able to forecast and plan.

Hypothesis: Agile estimation taps into human strengths by ensuring the workers never again have to talk about time or cost.

Time Frame: 6 weeks, ask pivot or persevere: every two weeks

Typical Outcomes: Decrease in team stress, while maintaining or improving estmation accuracy of work

Skill Growth Criteria: You have estimated your product backlog using fibonacci numbers, understand why fibonacci is used, and are comfortable to estimate any new piece of work in moments using your scale.

[AgileReview]

#NoEstimates :) I used to be pro story points. Overwhelming, it seems everything I have in favor of "public" story points (vs just using estimation as an internal team tool), has been disproven or been overwhelming abused in practice.

Anytime doing something the right way take hours and hours to explain because people (teams) just aren't getting it is an indicator that we may need to rethink our approach.