01 · At a glance
What are the signs a software project is failing?
The eleven signs fall into four groups: delivery, code, people and money. The table shows each sign and the check that tells you if it applies. Details follow below it. Read the software project rescue page if several are true for you.
| Group | Sign | Quick check |
|---|---|---|
| Delivery | 1. Dates keep moving | Has the same milestone slipped twice? |
| Delivery | 2. No release you can reproduce | Can someone build and deploy from the repository today? |
| Delivery | 3. Demos work, real use breaks | Does it fail with real data or more than a few users? |
| Code | 4. No automated tests | Is there a test run you can see pass or fail? |
| Code | 5. A fix breaks something else | Do unrelated screens change after a small edit? |
| Code | 6. Nobody can explain the structure | Is there a diagram or a README that matches the code? |
| People | 7. One person holds all the knowledge | What happens if that person leaves? |
| People | 8. You do not control access | Do you own the repository, cloud account and domain? |
| Money | 9. Spend rises, visible progress does not | Can you list what shipped in the last quarter? |
| Money | 10. Status reports avoid specifics | Do updates say what is done, in terms you can check? |
| Money | 11. Every estimate is a rebuild | Is the answer to every problem 'start again'? |
02 · Delivery
Which delivery signs matter most?
The strongest delivery sign is a release you cannot reproduce.
- 01
If nobody can build the code from the repository and deploy it to a clean environment, you do not own a working system, you own a snapshot that happens to be running.
- 02
Moving dates are weaker on their own, since estimates are often wrong. They matter when the same milestone slips twice and the new date comes without a changed plan. A demo that works but fails under real data is the third sign: it means the code was built to be shown, not used.
03 · Code
What code problems point to a rescue?
No automated tests is the code sign that costs the most later.
- 01
Without tests every change is a guess, so teams slow down or stop changing things. A second sign is the side effect: a small edit alters an unrelated screen, which means the pieces are tangled together.
- 02
The third is structure nobody can explain. If the original author cannot draw how the parts fit, a new team will have to reverse-engineer it. An independent code audit reads the code and writes that structure down, along with what is risky.
04 · People and access
Why does knowledge held by one person count as a warning?
One person holding the knowledge is a warning because the project stops if they leave, are ill or fall out with you.
- 01
It is common in AI-built apps, where one person prompted a tool and nobody else saw how it was assembled.
- 02
Access is the same problem in a different form. If the code, cloud account, domain or app-store account sits under a vendor's or a freelancer's login, you cannot move the project without their cooperation. Fix access first. The vendor handover checklist lists what to collect.
05 · Money
What do budget signs look like?
The budget sign is spend that rises while the list of shipped features does not.
- 01
Ask for a plain list of what reached users in the last quarter. If it is short, or if reports talk about effort rather than results, you are paying for activity.
- 02
The last sign is a team that answers every problem with a rebuild, before reading the existing code. Sometimes a rebuild is right, but the decision should rest on evidence from an audit. See the fix or rebuild rule on the hub page.
06 · Next steps
What should you do if several signs apply?
Secure access
Get ownership of the repository, cloud accounts and domain in your organization's name before anything else.
Pause risky changes
Stop new features while you find out what state the code is in.
Get an independent read
Ask someone with no stake in the current work to audit the code and report what is there.
Decide with evidence
Fix, rebuild or stop, based on the audit rather than on opinion. The team selection guide helps you compare options.
07 · Next step
How does Ace8 help with a failing project?
Ace8 is the modernization practice of AceMQ.
- 01
AceMQ engineers take over a stalled project, audit it first, stabilise it, add tests and a deploy pipeline, and get it to production. After go-live, AceMQ supports the result around the clock, see what happens after migration. The price is a quote on request, with a fixed price for the first audit agreed after a scoping call.
- 02
Request a rescue audit to find out which of the eleven signs your project shows, and what to do about each.