We all have days, weeks, even months when things don’t go according to plan. This can be true of software development where a project that begins well starts to go off the rails.

As infuriating as this can be, it often provides an opportunity to re-evaluate your requirements and improve the system beyond its original scope. The result may be a better system than you first envisaged.

It’s worth remembering what Thomas Edison said:

“I have not failed 10,000 times. I have successfully found 10,000 ways that will not work.”

Good now is better than perfect later

If a project starts to fail, having something is better than having nothing at all. A failing project is normally a few weeks or months into the plan or the development. At this stage, a good partner should help you evaluate the extent of your problem and identify which areas of the system to keep. This should be a straightforward process.

Any existing output can still be used for demonstration purposes which can be invaluable in getting a struggling project back on its feet.

Nearly all software implementations come up against problems at some stage and to be forewarned is to be forearmed. Here are three common causes of failure along with tips on how to avoid them.

Poor User Adoption: It’s vital to get the people who are going to use the system on board at the very start.

Avoid Project Delays: Communication is key to preventing delays and getting things back on track.

Scope Creep: Changes are inevitable, but how many and what kind are acceptable?

If your D365 project needs rescuing, get in touch to see how we can help.