Automated Governance Prevents Costly Mistakes
Posted by Jeff Papows on Wed, May 11, 2011 @ 04:33 PM
Let me start by saying that Dave Rosenberg has it right! Time and time again we see these cases and scenarios with our new customers. The kinds of risks being taken would seem, at least to me, logical but here are some of the reasons why so many risks today's IT organizations continue to happen:
1) Not having an automated governance platform that can manage any type of code development – whether it is happening internally or somewhere off shore.
2) Failing to govern all the application lifecycle management from the onset of its design to the deployment stage.
3) Not being able to quickly and effectively find policy violations that can cause exactly what Dave discusses here: a negative brand image and the loss customers and revenues, and by
4) Ignoring small glitches that can grow into the biggest challenge for an organization - after all - ignorance is bliss right?
It is not shocking to me to see that 40 percent of respondents said that third-party code resulted in delays or recalls, security vulnerabilities, increase in development or revenue impact when you consider that only a small amount of code actually gets reviewed by “centers of excellence” or COEs. One cannot expect an architect to sit through and read millions of lines of code to find the types of violations that we at WebLayers find everyday for our customers – not in weeks or days but in milliseconds.
Lets face it, when I wrote Glitch – The Hidden Impact of Faulty Software - I quickly realized that our industry suffers from complacency – We’ve become so dependent on technology – from our coffee makers to our cars - the fact that you almost need to be an engineer to take care of our cars should speak volumes as to how pervasive high tech has become.
Do you agree that software development should be governed from the first key stroke to the very last? Let me know your thoughts.
Jeff