←back to thread

268 points behnamoh | 2 comments | | HN request time: 0.633s | source
Show context
ohthehugemanate ◴[] No.28668571[source]
The research on this stuff says that time estimates are extremely inaccurate and to be avoided. If you manage to stay inaccurate by ONLY a factor of 3.14, that is unusually high accuracy.

Much more accurate are estimates of difficulty or complexity (small medium large, weighted numbers, whatever). The manager can then make an average conversion rate to time (with error bars), and use that for medium/long term forecasting. This is demonstrated extremely accurate compared to time estimation (but it is useless and breaks if you apply time/points pressure to your team, or even let them think in terms of a time conversion rate).

This is not new research. Kahneman's Nobel prize about decisions under uncertainty was in 2002. Put away the superstitions and stop estimating with time!

replies(1): >>28673774 #
1. spacemark ◴[] No.28673774[source]
So basically, engineers estimate complexity and the manager converts that to time? Still sounds like estimating with time to me.
replies(1): >>28702158 #
2. girvo ◴[] No.28702158[source]
> manager converts that to time

Based on past data, I think. But yeah it's still not great IMO, even if it might be slightly more accurate in some circumstances.