Recently, I described an IT failure at the Los Angeles International Airport that caused 20,000 passengers to be stranded while waiting to be processed through U.S.
Beyond IT Failure
Michael Krigsman is a recognized authority on the causes and prevention of IT failures.
Michael Krigsman is an internationally recognized analyst, strategy advisor, and authority on enterprise software leadership, CIO innovation, and social business. Interact with Michael on Twitter at @mkrigsman.
In a post called Can you spray paint innovation?, fellow Enterprise Irregular, Vinnie Mirchandani, raises an important issue regarding pockets of creativity inside SAP and Oracle.
Fellow ZDNet blogger Joe McKendrick poses the question, "How do we really know when SOA ‘fails’?"Here are a few choice quotes:What does SOA failure look like?
Chalk up another massive IT problem for Her Majesty's government in the UK. According to InterGovWorld and the Financial Times, the UK has bidding has opened on a controversial multi-billion pound identity card program called the National Identity Scheme (NIS).
Liam Durbin, CIO of GE Fanuc Automation, writes in CIO magazine about five common scenarios that can cause software implementations to fail:1. Just replace the homegrown system with a package—no need to involve the functional teams.
Over the last year, I've railed against Oracle for its arrogance in the face of major project failures. We're talking world-class, spit-in-your-face arrogance here.
Recently, I described failures in several Enterprise 2.0 and Web 2.
CNN and the LA Times both report failure of the international arrivals screening computers at Los Angeles International Airport failed. As a result, 20,000 arriving international passengers had to wait many hours while the system was repaired.
Just yesterday, I described poor reliability as a key weakness in the Enterprise 2.0 model.
All over the blogosphere one hears talk of Enterprise 2.0, in which lightweight software tools are predicted to encroach upon, and perhaps ultimately even replace, big software systems.