5 ms·

They are hours I'll have to eat because I did not properly estimate how long it would take to complete that portion of the project. Why is this such an accepta

They are hours I'll have to eat because I did not properly estimate how long it would take to complete that portion of the project. Why is this such an acceptable premise?

ams6110 15y ago
Good question, actually. How often does one take a car in for repair, receive an estimate, and then later get a phone call "we found that XYZ part is worn out, we need to replace that as well, it will be an extra $500."
- vannevar 15y ago
  A crucial difference is that the mechanic has possession of your car, and the legal right to keep it until you pay for the work that has been done on it up to that point.
  - zacharydanger 15y ago
    How does that not apply in the same scenario? Tell the client what you've run into and what the new estimated cost to actually implement the feature. Unless the contract has some stipulation about misestimation, no one can force you to do that extra work.
    - vannevar 15y ago
      In the mechanic's case, he has the car. The client presumably was using the car already (unlike your software project) and needs it immediately. His only other choice is to pay you, get the car back, and start over with another mechanic. That generally gives the mechanic more leverage. You're right, no one can force you to keep working. But typically at that point the client owes you money, you have no tangible collateral in hand (like a car) and while you might be able to force him to pay by suing him, it's generally going to be a lot cheaper in the long run to eat the hours and keep the client. If the project is grossly underestimated and the client is unlikely to provide more large projects in the future, then quitting the project might make more sense than continuing. In which case, depending on the nature of the contract and the project, the client might end up suing you.
vannevar 15y ago
Anchoring. By giving the client an estimate, you anchored their expectations. Considering also that you're in a competitive environment where competitors are systematically incentivized to underestimate projects in order to get work, and the reality is you will end up eating some hours.

They are hours I'll have to eat because I did not properly estimate how long it would take to complete that portion of the project. Why is this such an acceptable premise?

ams6110 15y ago

Good question, actually. How often does one take a car in for repair, receive an estimate, and then later get a phone call "we found that XYZ part is worn out, we need to replace that as well, it will be an extra $500."

vannevar 15y ago
A crucial difference is that the mechanic has possession of your car, and the legal right to keep it until you pay for the work that has been done on it up to that point.
- zacharydanger 15y ago
  How does that not apply in the same scenario? Tell the client what you've run into and what the new estimated cost to actually implement the feature. Unless the contract has some stipulation about misestimation, no one can force you to do that extra work.
  - vannevar 15y ago
    In the mechanic's case, he has the car. The client presumably was using the car already (unlike your software project) and needs it immediately. His only other choice is to pay you, get the car back, and start over with another mechanic. That generally gives the mechanic more leverage. You're right, no one can force you to keep working. But typically at that point the client owes you money, you have no tangible collateral in hand (like a car) and while you might be able to force him to pay by suing him, it's generally going to be a lot cheaper in the long run to eat the hours and keep the client. If the project is grossly underestimated and the client is unlikely to provide more large projects in the future, then quitting the project might make more sense than continuing. In which case, depending on the nature of the contract and the project, the client might end up suing you.

vannevar 15y ago

Anchoring. By giving the client an estimate, you anchored their expectations. Considering also that you're in a competitive environment where competitors are systematically incentivized to underestimate projects in order to get work, and the reality is you will end up eating some hours.