16

Company wants me to give a rough estimate of developing a new feature in a distributed legacy monolit. They told me they would inform me the next day and want the estimate on the same day for a project that will probably take 2 devs 3-4 months. I ask for more time and info, give the estimate and they say it "feels too much". I mean ok. Then why am I even estimating? If in the first place the client has only X money than do the project for X and it doesn't really matter how much work it is, does it?

Comments
  • 5
    This is a classic!
    "Please estimate the time for this, but it can‘t be more than X days!"
  • 3
    It’s simple to make quick estimates when you’re told what the estimates should be
  • 1
    When you've completed what is actually possible, be firm with "it feels like this is what you said you wanted."
  • 0
    it turns out the real reason why it is too much is that a pm already estimated this (works no longer on the project ) and they calculated that this will be x and they are now surprised that this cannot be done within the budget which was estimated by a non technical person.
Add Comment