4 ms·
Let's say that you have 20 tasks. Each involves rolling a 10-sided die. If it's a 1 through 8, wait that number of minutes. If it's a 9, wait 15 minutes. If it'
by palish 15y ago
Let's say that you have 20 tasks. Each involves rolling a 10-sided die. If it's a 1 through 8, wait that number of minutes. If it's a 9, wait 15 minutes. If it's a 10, wait an hour.
That is a beautifully accurate description of modern software development. I hope you get quoted.
- gry 15y agoIt mirrors my experience as well. For about 6 months, management wanted us to time against user story. At the time, we used scale from 1 to 5. The concern was estimates weren't linear and for planning, a 5 one point story did not equal 1 five point story. Then, we ran the numbers. This was our graph for median time for a swag: | * | * | * | * |* |--------- 1 2 3 4 5 The ah-ha for management was the standard deviation. The more points estimated, there was greater and certain variance. We went to fib, because it felt more natural with the effort. The end result is if a story is estimated on the end, everyone knows there isn't enough information, it's a black hole or it should be broken down.
- groovy2shoes 15y agoShall we call it "planning craps" by analogy with planning poker?