I figure out a given time frame for a given solution plus 20% added time for estimate screwups(a number that over the years kinda works). I then manage the expectations of the requestor to expect a longer time frame than that for it to be done. Result is always on time and under budget. Example A mainframe group was expecting a 3 month rollout of jailed chrooted sftp. When I announced a 3 week rollout the manager was ecstatic(before the meeting I had already done the work knowing these folks were deliberately misled by a former employee on the dificulty) then after on week of nailing it down said lets change the JCL that moves stuff. The mainframer who was pretty bright said he could make the landing change pretty quick but wanted upper management to sign off. Upper management was ecstatic. The first rule of managing promises is managing client expections. Always offer at least 3 alternatives fairly thought out. Fastest, Safest and Cheapest with the drawbacks of each one clearly defined and get it in writing.
thanx,
bill
ya wannit done right or ya wannit now
poor people have poor ways of doing things(on the cheap, not bad, for the hignorant amongs ya)