Is there a good reason to estimate time for functions that make up months?

Today I was in a meeting with a consultant (consulted with us on internal procedures), and we went through planning planning for the next three months of development. I am not against this at all, I think it is important to have an idea of ​​what will happen next, in what order and relative values. I also find it great to set goals for what you would like to do on specific dates. But I always thought that this disagreement with this consultant and some members of my team who tried to put time estimates (even freely for several days and weeks) on the implementation of functions (which were not specified or even discussed in the end) was completely meaningless and useless task. In my experience, by the time I start working on it,this function will change dramatically or will include much more than I could know.

I leave the base and lose value in time and energy, on the assumption that in 2 months it will take 8 days (including HL ) of my time to implement FeatureX?

+3
source share
7 answers

It really depends on which assessments will be used and what expectations are applied.

If estimates are used to report to management without reservation, this can be a dangerous practice. If, on the other hand, they are used for high-level planning or for developing a project plan for discussion, then these estimates can be extremely useful.

WAG (wild ass guess) . +100%/- 50%. , , Ball Park, +50%/- 50%.

+4

, , .

, ... , . , , . . ", , , ... , - , // , , , , ".

?

+3

, , , . ​​ (.. 4 8 ). , . , , , , . , . , , , .

+2

, . , , . , , .

- ", N ", , , : " , N , 4N ?" , , .

+1

, , - Rapid Development Steve McConnell. - , , , , ( ).

+1

: , , , . , , .

, , : , .

, - , , . , . , , .

? ? ? , , , ?

, , .

0

, , .

, A, B, C, D E, . . , E . , . , , , . , ( ), A, B, C D. ,

.

, , , .

.


: , , ;-) , , . . . .

, . , - ( ).

-1
source

Source: https://habr.com/ru/post/1713617/


All Articles