Considering Software Modifications?
Posted by Kate Wilson on Tue, Jul 07, 2009 @ 07:56 AM
Working for a software company for the past few years I've come to observe our software services department working all day on complex modification's. I've come to notice several benefits but also consequences with modifications especially when they get too involved.
At our company, we normally try to sell all of our software "out of the box" just as it was written whenever we can. In our industry it's by far the easiest way to do business and allows for the fastest delivery and ROI for the customer. However, we also want to ensure that each software package is going to be the best fit for each client. Often times it's easy to make a few minor modifications to a software package to accomodate for exactly how the customer plans to use it. By doing so we can tailor our packages to each clients needs which can be a great benefit for the customer but at times can be a disadvantage in the long run. For example it may become a burden if the software becomes too customized for a particular client. With highly customized software we run into issues when its time to upgrade and additional modifications may be required. This means the client may not fully benefit from minor upgrades and bug fixes. They may have to purchase a customized support contract or training. And, there are always extra costs associated with our engineers development time to make sure everything is working properly. So, if you plan on having a customized software solution developed solely for your company and its use, I would recommend keeping track of all documentation and ensure you are aware of potential future costs associated with maintaining your software investment. On the other hand, a minor modification can provide increased efficiency and ease of use tailored to your business needs.
Some advice when considering software modifications:
- Ask your developer if they have performed this modification before. If it's been done before the developer will have all the documentation and will know how to adequately provide support moving forward. Easy.
- Ask about any future costs associated with maintaining your investment.
- Make sure the modification is truly necessary and beneficial for your needs, is this going to expedite your ROI?
- Make sure the software installation will fit your time frame. How long will the modification take to develop? Also, schedule a tentative completion and go live date.
- Take action to ensure you will receive proper training and support in the future.
- Most importantly know what your up against and how involved your modification is. If it gets too customized, you may be getting into more than you bargained for. Modifications should be developed as an added benefit, not a cost.
When have you run into trouble with modified software? Or, when has it benefited you?