4 ms·
This is also why I like estimating tasks using the Fibonacci scale without a direct correlation to time. In my teams, we generally set 8 points as something th
by __alias 6y ago
This is also why I like estimating tasks using the Fibonacci scale without a direct correlation to time.
In my teams, we generally set 8 points as something that would take an entire day. Every number after that jumps up in relatively large increments as they are more difficult to accurately determine
- BOOSTERHIDROGEN 6y agoInteresting take, mind sharing how do you use fibonacci ? Thanks
- bart3r 6y agohttps://www.youtube.com/watch?v=iZYSapFCg4A https://www.youtube.com/watch?v=iZYSapFCg4A
- redis_mlc 6y ago0, 1, 1, 2, 3, 5, 8, 13, 21, 34, 55, 89, 144, 233, 377, 610 Hope (Days) = Calculated Est. (Hours) 1 day = 8 hours 2 days = 8 + 13 = 21 hours 3 days = 8 + 13 + 21 = 34 hours H(days) = Fn(6+days) hours, where days >= 2
- mgkimsal 6y agoNot the OP, but one of the teams I'm on uses fib somewhat differently. Any point with 1-2 is estimated at < 1 day. Some are literally 20 minute fixes, but ... you don't always know that up front, you just generally know it may be pretty small. 2 might sometimes go up to a day. A 3 is assumed to be a day or two. A 5 is assumed to be 3-4 days. An 8 would be 1-2 weeks. Anything higher is backlogged until it's broken down into smaller segments. Not sure how well that compares to usages by other teams, but that's one data point for your question.
- deleted 6y ago[deleted]