3 ms·
> Or try to negotiate with the estimate. Which means they aren't estimates any more. Oh yes this annoys me. I've been asked to break it into sub tasks then jus
by bbcbasic 10y ago
> Or try to negotiate with the estimate. Which means they aren't estimates any more.
Oh yes this annoys me. I've been asked to break it into sub tasks then justify those. So best case estimates based on some predicted sub tasks ... before any design has been done! Then the surprise when it takes longer
- jacques_chester 10y agoAs a note, breaking into subtasks does improve estimate accuracy on just about anything, due to the "unpacking effect". Humans routinely underestimate the time and difficulty involved in just about everything. Breaking a task down into subtasks leads to higher estimates which will typically be more accurate. You are of course being asked to do something very difficult. In 3-point estimation schemes, you'd give back very wide bands for a few subtasks that you identified. Maybe point at the cone of uncertainty a few times. I know it often doesn't work. To me, most of the problems with estimating aren't with the estimating.
- bbcbasic 10y agoThat's true the problem here is the negotiation process. If you have a technical manager they can use the technical hat to argue the estimate down. And the manager hat is the motivation to do so. I kinda prefer the planning poker where all members are encouraged to have equal say and there is no power imbalance