Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

My developer's estimates are always wrong

Short answer

Software estimates miss because unknowns are hidden, scope shifts and hidden work appears during the job. A better estimate names its assumptions, splits the work into small parts and shows what is not yet known. Ask for that rather than a single date.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • Each feature takes about twice as long as quoted.
  • I only learn about delays at the deadline.
  • Estimates are one number with no explanation.
  • Extra work keeps appearing mid-project.
  • I no longer trust any date I am given.

Why does this happen?

  1. Unknowns are not named

    A single number hides what is not yet understood, such as an unknown third-party system or unclear rules.

  2. The request is vague

    If it is unclear what done means, each side imagines a different feature.

  3. Hidden work is left out

    Testing, releasing, fixing review comments and talking to others take time and are often missing from the estimate.

  4. The estimate becomes a promise

    When an estimate is treated as a commitment, people give optimistic numbers to please.

What can I do about it today?

  1. Write down what done meansFor each feature, write what a user can do when it is finished, and what is not included.
  2. Ask for the assumptionsAsk your developer to list what the estimate depends on and what could change it.
  3. Ask for a range with the reasonsRequest a likely and a worst case, and what would move it from one to the other.
  4. Split large work into stagesAsk for smaller pieces you can see and approve, so a miss shows up early.
  5. Review actual against estimateAfter each piece, compare the time taken with the estimate, and talk about why.

When should I bring someone in?

  • Estimates have been wrong several times in a row and the gap is not explained.
  • Large budget or launch dates depend on one estimate.
  • Your developer refuses to explain how they estimated.

How do I handle it?

  1. Clarify the featureI write the feature in plain words with what is in and out of scope.
  2. Name the unknownsRisky parts are listed, and where practical a short investigation is done first.
  3. Give a rangeThe estimate comes as a range with assumptions, and it is updated as facts arrive.
  4. Work in visible stepsYou see working parts regularly, so a slip is visible early.
  5. Compare and learnActual time is compared with the estimate so the next one is better grounded.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Are good estimates possible?

They can be reasonable, but never exact. Their value is in showing assumptions and uncertainty, not in a precise date.

Should I add a buffer myself?

You can, but better is a visible range with named risks, so the buffer is explained.

Is my developer incompetent?

Not necessarily. Consistent misses usually point to a method problem, hidden unknowns or unclear scope.

How was this page made?

I drafted this page with AI assistance. It is general guidance for business owners, not advice for your own system. Found a mistake? Tell me.

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.