The team sits together, everyone has a deck of cards with values. The team lead calls out a task and everyone throws down his estimate at the same time. If the values diverge widely, the team lead asks the outliers to explain, and everyone can reconsider after the explanation. The highest remaining number is taken as the estimated time.
This was done in days for big tasks, who where then split up in sub-tasks where the same was repeated in hours.
Sharing the responsibility of estimates prevents the manager-pressure problem you talked about. If the team estimates it takes 5 days and the manager thinks it should only take 3, the team isn't going to back down (unlike what could happen in 1-1 conversations), and the manager will ignore the estimate at his own peril.
http://www.codinghorror.com/blog/2007/10/lets-play-planning-...
Some people have little, or no, idea the effort required for a task. Fair enough, just don't base plans on known ignorance. Compelling them to vote is silly.
Some people have differing notions of "done". One self-appointed hotshot may be able to crash thru the code and make something run happy path in a few hours and thus gives a low estimate, but unlike others fails to account for ripple effects, breakage, documentation, consulting with others, etc. Are votes for "it works"? or "everything related is completed"?
All too often outliers are right, but dismissed because they're outliers and given just a few impromptu seconds to explain complex nuances why they're right and the disinterested opposition is wrong. Subsequent "I told you so"s much farther down the road are disheartening, and kept quiet as the opposition still doesn't see the connection nor want to.
Again, make sure the estimate includes all related work. Implementation may be quick; integration testing or documentation may be long. Don't give something a 3 to do and ignore the additional 5 needed for ripple effects.
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
The most important difference is that fully dressed Wideband Delphi provides anonymity to the estimators. The goal is to avoid allowing estimation to become a venue for status play or kabuki theatre.
The manager gets credit for success, and the developers get the blame for failure.