Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

My software project keeps growing and never seems to finish

Short answer

Projects rarely finish when the goal is described as a list of ideas instead of an outcome with an end point. Decide what a first usable release must do, write down what is left out, and treat every addition after that as a swap or a later release, with its effect on the date stated.

  • 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 and nobody can say when it will end.
  • Each meeting adds another small feature, so the list never gets shorter.
  • My developer says it is almost done, but a new problem appears every time I test.
  • I cannot tell which parts of the work are essential and which are nice to have.
  • The budget or time is used up and I still have nothing real customers can use.

Why does this happen?

  1. The finish line was never written down

    If the project is described as an app like the big ones, there is no point at which anyone can say it is done. A finish line needs a short list of things a user can do, tested and working.

  2. Small additions feel free

    Each extra button looks tiny, but it also needs design, testing, edge cases and later maintenance. Twenty small additions add up to a different project.

  3. Real needs appear only once people use it

    Seeing a working version shows what was missing. That is normal, but it belongs in the next release, not in a version that has not shipped yet.

  4. Some growth is hidden work, not new wishes

    Sometimes the list is not growing at all: the original request contained work nobody spotted, such as logins, error handling or admin screens. Telling the two apart needs an honest written breakdown.

What can I do about it today?

  1. Write what a first release must doDescribe in a few plain sentences what a customer must be able to do on day one. Everything outside those sentences is a later release.
  2. Keep a not-now listPut every new idea on a separate list instead of the current one. Nothing is lost, and the current work can finish.
  3. Ask for a breakdown with sizesAsk your developer to list the remaining tasks and mark each as small, medium or large. A written list shows what is genuinely left.
  4. Mark what is new and what was always neededGo through the remaining items and note which were in the original request and which came later. That tells you where the growth came from.
  5. Ask what the earliest usable version isAsk what could be released soonest if you dropped the least important items. A small real release teaches more than a large unfinished one.

When should I bring someone in?

  • You are paying for the project and cannot judge whether the remaining work is reasonable.
  • Your developer or agency gives only reassurances and no written list of what is left.
  • The project has to be released for a real deadline such as an event or a contract.

How do I handle it?

  1. Write the first-release scopeA short written scope: what the user can do, what is out, and how each item will be checked as done.
  2. Split the backlog into threeMust be there at launch, should come soon after, and can wait. Only the first group blocks release.
  3. Price changes in timeA new request is answered with what it adds to the work and what it would move, so you can say yes, later or swap.
  4. Release early and in stepsI prefer a small version that real people use over a long build, because use is what shows what is really missing.

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?

Is a growing scope always my fault?

No. Hidden work in the original request, and needs discovered by testing, are common. Writing it down separates what is new from what was always there.

Should I stop adding features altogether?

Stop adding them to the release in progress. Add them to the next one.

Can a project be too big to finish?

It can be too big to finish as one release. Splitting it into smaller releases that each stand on their own is usually the way out.

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.