What makes up the total cost of testing?
Testing is critical to the success of any large scale enterprise IT project. Testing is bought on a day rate, and the cheapest bidder often wins. This method of selection often leads to costly, time-consuming testing phases that ultimately make testing far more expensive than initial projections.
So how do you keep the total cost of testing down? Here’s our take on what to consider to avoid a big overall testing cost:
- Focus on the quality delivered, and the impact that the potential provider will have on the actual business. You want your chosen provider to be 100% on “your side” when it comes to negotiating with other contractors who may need to be pushed to deliver the right quality work for the project. Larger, cheaper providers may have ongoing engagements with these suppliers that make these difficult conversations over quality politically unpalatable for them to take on, meaning you ultimately lose out or end up paying more.
- Bear in mind that time is another cost factor. Cheaper day rate providers will often demand more time from your business in order to get the knowledge and the knowhow to test effectively. This will mean that they need to be micromanaged from your own business, which can leads to pressure in other areas and in the worst case delay due to the lack of internal resources to “take on” the task.
- Not all testers are created equal. There are multiple specialisms within the field of testing – at Experior all our consultants are experts in SAP, e-commerce, performance testing, automation and data center migrations. Hiring a provider with specialists in the field has many benefits, but from a cost perspective, one of the largest is that we’re able to talk the same language as your developers. This means when analyzing and assessing risk, if you don’t know the terminology of the developers to describe the processes, you’re immediately on the back foot and can end up losing crucial pieces of information “in translation”.
The final cost of testing you must consider is compromise. In our modern working careers we have become accustomed to compromising on certain aspects of a given job or prospect in order to achieve a goal – reducing quality to increase speed is a common one. The testing phase should not in any way bring about a compromise on the requirements of a software project. Your testing company should be matching up the business requirements and delivery – and working to make those happen. At no stage should there be a situation where a sacrifice must be made in functionality or the quality of the solution once the project makes it to the testing phase – this should be highlighted far before then, and working with a testing partner that understand your business can help mitigate the risk of this scenario happening.
Ultimately it’s difficult to see the big picture when you’re not a testing expert yourself – if you’re looking for a quick set of questions to ask your testing provider, we’d recommend your quiz them on their approach to testing, their plan for working with you and how they will be reporting back to you.
If you want to learn more about what a consultative approach to testing can do for you and your SAP project, feel free to contact us and we’d be happy to chat with you further.
Originally posted July 15, 2015, by Christian Moreno, Experior Group