Staying ahead, or even just keeping up means frequent change. But when any application change is introduced it has to be seamless and as straightforward as possible – and it can’t do anything to disrupt business as usual.
This is where the issues of application testing and quality assurance (QA) come to the fore. Testing and QA are an increasingly important, but often undervalued, aspect of change. It might be change imposed from a third party platform, change driven by the business, or change that has bypassed the IT process and been implemented directly by the business. But in all cases, releasing change without proper validation will lead to disaster.
Sadly, some heads of organisations often regard it as a tick box, operational function – a costly overhead. And it can be costly – developing test plans, executing tests and supporting user acceptance testing, it’s all a time-drag on the business. It can be a significant cost, but it can be more significantly a major bottleneck to implementation and realisation of the change objectives. However, this cost is inconsequential compared to the cost of getting it wrong.