[coldcode]

If you build a general ledger application for the 10th time, sure forecasting is fairly straightforward. Nothing I do at my (very large, non tech but highly software driven) employer has ever been done before here. All estimates are treated officially as if they are date time accurate, but changes happen during the lifetime of the project so often you may as well use a random number. I call it a "nod nod wink wink" estimate: every wants it to be accurate, but no one really expects it to mean anything, other than the budget people.

[waheoo]

One of my favorite managers required i give him estimates.

I hated it because we both knew the number was bullshit.

On the other hand, having to think about the estimate and give him something, even if at times it was a guess, i still found it beneficial. It meant i focused better, stayed on task, and often delivered on time anyway.

Im not saying everyone needs the accountability rails, but some people excell with this particular helper.

[someguyorother]

"Plans are worthless, but planning is everything."

[waheoo]

Indeed!