News for hackers. Stuff that matters.
Re:Poor developer estimates, a.k.a. guesstimation by jacques_chester on Sunday September 15, 2013 @10:19AM (#6389153)
I think you're mixing bids with estimates.
Re:Poor developer estimates, a.k.a. guesstimation by InclinedPlane on Sunday September 15, 2013 @10:25AM (#6389166)
Is there some Universe where developer time is not synonymous with cash money dollars?
Re:Poor developer estimates, a.k.a. guesstimation by jacques_chester on Sunday September 15, 2013 @10:28AM (#6389175)
No, I mean, the process of inviting tenders or bids is distinct from estimating.

Bidders will inevitably perform some sort of estimate, even if it's only a wild guess. But even the most rigorous internal estimation process may then be passed to management or sales staff who will use it only as a starting point for the bid.

The estimate didn't change; instead it was an input into the bid.

And in as the grandparent comment demonstrates, buyers often pick the lowest bidder.

Re:Poor developer estimates, a.k.a. guesstimation by rfergie on Sunday September 15, 2013 @11:16AM (#6389297)
Yes, I think you are right.

But after reviewing my comment I think it is a point that is still worth keeping in mind.

The same kind of thing could happen internally within a company or even subconsciously within a developers mind.

Re:Poor developer estimates, a.k.a. guesstimation by jacques_chester on Sunday September 15, 2013 @11:18AM (#6389305)
Yes, absolutely.

The problem is that business documents like a bid, an estimate, a goal, a plan and so on all share similar surface features. So it's easy to mix them up.

The classic is "that estimate is too high. Change the estimate".

Conceptually, an estimate is an immutable object. What you're really being asked for is a new estimate that is closer to a goal.