There has been a large change in the last decade in how software is built and used. With the ability for anyone to build an app and market it, many organisations have realised that it is ‘easier to buy than build’. There are unique applications that are still being built (many of them) but for regular business functions and even some unique business functions it is often better and more effective to buy. A lot more functionality is available in the purchased package than could be built internally for the same cost.

However the end result of this is that the Quality Assurance and testing aspects are frequently overlooked because they should have been taken care of by the vendor. However, most EULAs do not provide any assurance that the product works or provides valid results or information. Usually they state the opposite, there is absolutely no promise made of any ability to rely on the results. Thus you are on your own for the Quality Assurance (‘QA cannot be outsourced’).

What tends to be overlooked in the rush to acquire the package is that considerations for QA need to be made at the time the purchase is being considered. They become part of the contract or requirements to ensure that the package is most of the way to fulfilling our needs before it arrives on site. We don’t want to be in the position of trying to change a package after it has already been purchased.

Take a look at some of the seminars that we offer that address this situation and see if they apply to your situation. Considering the Quality Assurance and testing aspects early can save you a lot of effort, time and funds later on.

Contact us for further information.
Photo by Carlos Muza on Unsplash