If programmers are bad at estimating because they feel pressure to produce short predictions, the above method will prevent this.
If programmers aren't even asked to estimate or ignored, obviously the problem is not that programmers are bad at estimating.
The method can fix some potentially harmful management<>programmer interactions. It can't fix stupid management.
So the manager can pass the buck.
>>If programmers aren't even asked to estimate or ignored, obviously the problem is not that programmers are bad at estimating.
Yes. I would argue most of the time when projects take longer than predicted it wasn't the programmer's estimation that was the problem.
>>The method can fix some potentially harmful management<>programmer interactions. It can't fix stupid management.
Agreed
If programmers are bad at estimating because they feel pressure to produce short predictions, the above method will prevent this.
If programmers aren't even asked to estimate or ignored, obviously the problem is not that programmers are bad at estimating.
The method can fix some potentially harmful management<>programmer interactions. It can't fix stupid management.