Why software projects go wrong
Software projects seldom fail because of the programming. They fail because of unclear goals, rushed decisions and poor communication. These eight mistakes are avoidable, and avoiding them costs nothing.
1. Starting without a written scope
If the features are only agreed in conversation, each side remembers them differently. Write down what is included and what is not before any payment.
2. Choosing only on price
The lowest quotation often leaves out testing, training, data migration and support. Compare what each quotation includes, not only the total.
3. Building everything at once
A first version with every imaginable feature takes long and is hard to test. Launch the part that solves the biggest problem, then add modules.
4. Leaving out the people who will use it
Owners approve software, but accountants, receptionists and store keepers use it. Involve them early; they know the real process.
5. Ignoring existing data
Years of records in Excel and registers have to be cleaned and moved. Plan time and budget for it from the start.
6. Skipping testing with real work
A demonstration with sample data always looks fine. Run a real day's work through the system before going live.
7. No training and no handover
Staff go back to the register if nobody shows them the new way. Ask for training in Nepali, a user guide and the administrator logins.
8. Not agreeing on ownership and support
Confirm in the contract who owns the source code and data, where it is hosted, how long free support lasts and what later changes cost.
What a healthy project looks like
- A written scope and milestone payments.
- A working demonstration every one or two weeks.
- One contact person on each side.
- Changes requested in writing, with the cost agreed first.
- A test period before launch and support afterwards.
For the next step, read how to write a requirement brief and the twelve questions to ask a software company. Our software development service follows the process above.
