Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

My software project is late, over budget and going nowhere

Short answer

A stalled project is rescued by finding out the truth, not by adding people. Stop the open-ended spending, get an independent view of what is built and working, and cut the scope to a first version that can be released. Then decide whether to continue, change the team or restart on the parts that work.

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

Does this sound like your situation?

  • The launch date has moved more than once.
  • Every status update says almost done, and nothing can be shown.
  • The budget is spent and the main feature does not work.
  • The team keeps changing, or the developer cannot say what is left.
  • I do not know whether to keep going or stop.

Why does this happen?

  1. The scope grew without a first version defined

    When every idea is added to the first release, nothing is ever finished enough to ship.

  2. Progress was reported in words, not in working software

    Updates like seventy percent done mean little. Only a working screen you can click through shows real progress.

  3. Nobody on the business side could judge the work

    Without a technical person on your side, problems stay hidden until the money has gone.

  4. The foundations were wrong for what was needed

    A weak design in the early weeks, on data or on how parts talk to each other, makes every later feature slower.

What can I do about it today?

  1. Pause open-ended spendingAgree a short stop or a fixed small piece of work. Do not keep paying for time without a visible result.
  2. Ask to see it runningA walkthrough of what actually works today, on a real device or site, not a slide deck.
  3. Write the first version in ten linesThe smallest set of things a real user needs to do, in your words. Everything else goes into a later list.
  4. Collect the contract, the brief and the paymentsA review needs to know what was promised and what has been paid for.
  5. Secure the code and accountsMake sure a full copy of the code and the accounts the project uses are in your hands, before any difficult conversation.
  6. Do not fire the team before you know what you haveMoving fast can lose the only people who know the system. Decide after the review.

When should I bring someone in?

  • The money or time already spent makes the next step feel like a gamble.
  • You need a neutral view that is not from the team doing the work.
  • There is a market date, a funding round or a customer waiting.

How do I handle it?

  1. Find out what is really builtI run what exists, read the code and list what works, what is partly done and what is missing, with no blame.
  2. Cut to a releasable first versionWith you, I choose the smallest version that could be released and put everything else behind it.
  3. Give you the options and the risksContinue with the current team, change the team, or restart parts of it, each with what it would mean, so the decision is yours.
  4. Run it in short, visible stepsWork in small steps you can click through each time, so you see progress as working software.

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?

Should I stop the project?

Not before you know what exists. Some projects need a stop, many need a smaller scope and a clear first release. The review shows which.

Will you take over the whole project?

It can be reviewing only, leading the work, or doing part of it. The scope is written down after a short discovery call.

Can the money already spent be recovered?

That is for your contract and a lawyer. I can describe what was and was not delivered in plain words.

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.