http://qs321.pair.com?node_id=987832


in reply to My project estimates are based on:

For me Perl is a hobby (strictly for my own fun, or for fiddly things I can do "under the radar")

However I'm paid to implement SAP BPC systems and have found that no matter how optimistic or pessimistic I am in my estimate, the #1 rule is that the client will ALWAYS try and "negotiate" for less time. Initially I reacted by becoming more pessimistic and then delivering faster than planned, but found that clients aren't grateful ... they just take it as a sign you were planning to rip them off.

So now I estimate as accurately as I can, and when the client objects, I ask them to pick the functionality that's NOT going to be implemented.

Only one client has ever accepted the challenge ... and they decided they didn't need any project documentation! :-) ... I've since made more than 3 times the "saved" money out of them afterwards, because they had no idea how to support the system and had to keep calling me in.

So Long
blackstarr

Replies are listed 'Best First'.
Re^2: My project estimates are based on:
by swampyankee (Parson) on Dec 29, 2014 at 16:56 UTC

    Long ago, at a company that has since been purchased twice, one of the project engineers was famous for writing up his estimates for the exact amount, with no padding. On more that one occasion, somebody in the finance office would automatically cut 20% off, then someone else would yell at him for going over the budget. His response was usually something to the effect of "I told you how much time and money was needed; this guy changed my estimate. I know what I'm doing, and I don't put in padding just so it can be cut so some bean counter can look like he's doing a real job."

    This only worked because the person who did the cutting was not the same person as the one yelling about going over budget ;)


    Information about American English usage here and here. Floating point issues? Please read this before posting. — emc