Would More I.T. Governance Helped McAfee’s Global Software Glitch?

The news of McAfee's global security update gone awry has been the target this week of what is being widely dubbed as a computer glitch.  Apparently, its antivirus update program froze computers by misidentifying a common Microsoft Windows file as a virus causing the computers to keep rebooting.
 
The impact is being felt in businesses of nearly every type.  Over 1,000 Coles Supermarkets throughout South Australia, which is about 10 percent of the chain, were shut down due to the glitch that shut down the cash registers.  In Rhode Island, several hospitals had to turn away non-trauma patients and reschedule elective surgeries.  In Lexington, Kentucky more than 1,000 government and school computers, including those at police stations, were shut down due to the glitch.
 
Not surprisingly, McAfee addressed the technical issue within a few hours and their public relations team was in full force to clarify the issues behind the glitch that solely affected computers running Microsoft Windows XP with Service Pack 3 installed.
 
While I suspect distributing the global patch to subscribers is more than a routine task at McAfee, I have to wonder what went wrong this time.  It's an interesting question from the standpoint of I.T. governance.  How is it that a glitch can appear seemingly out of nowhere in a process that's done on a regular basis?  The folks at McAfee outline the details here.  However, the end users are still up in arms about the glitch.
 
It appears that McAfee did all the right things to recover from the public flogging associated with this glitch.  Behind the scenes, I'm going to venture a guess that there's a very detailed analysis and review of how exactly that glitch made its way out to the global customer base.  And I'm going to wonder just how much IT governance was in place and how it may have potentially avoided the issue altogether.