A big challenge is current IT is that most of the software is COTS (Commercial-off-the-Shelf for the acronym impaired).
If you have a piece of bespoke software, and you discover something that clearly doesn't meet the requirements, it's a bug - no questions asked.
If you have a COTS application, it's a feature request to be prioritized in some future release, if you are lucky.
The obvious problem this creates is that you end up stuck with a bug, but it is really far more insiduous. When your bug list is topped with things that your team has little power to address it is very demoralizing. Why should the team put all this effort into testing, when it will be a over a year before anything will be done with most of the results.
...and enterprise software vendors wonder why companies are so slow to upgrade...
No amount of testing will overcome this. You just end up standing there between a rock and a hard place. You have put the project in sleep mode until the issues are addressed, you can "accept the risk" and move forward, or you can swap out the problem component at considerable cost and expense - assuming that is even politically possible.
...or you can just not bother to do thorough testing and act surprised when things go wrong.
I'm not saying I don't believe in thorough testing. By god I do. But it clearly isn't rewarded.
Discussion on:
Message 8 of 1
The best of ZDNet, delivered
ZDNet Newsletters
Get the best of ZDNet delivered straight to your inbox
