Recently, I blogged about an excellent report, released by the UK National Audit Office, on the subject of IT project failures. That report examined 24 IT projects, to draw conclusions about the causes of both project success and failure.
Beyond IT Failure
Michael Krigsman is a recognized authority on the causes and prevention of IT failures.
Michael Krigsman is recognized internationally as an analyst, strategy advisor, enterprise advocate, and blogger. Interact with Michael on Twitter at @mkrigsman.
Back in the 2001 time frame, the Office of Government Commerce (National Audit Office) in the UK established a program for avoiding large-scale IT failures. The program, called the Gateway Process, established a series of evaluation milestones, or gates, against which a project must be reviewed over its lifecycle.
I write this blog and see lots of weird stories, many of which I find hard to believe. Today’s topic is a good example, and deals with manipulative behavior justified in the name of innovation.
Following up on a post about IBM packaged services, Prashanth Rai from the CIO Weblog asked me the following question in an email:Yes, it looks like IBM is trying to do something that could really turn into tangible benefit for services customers. This seems to be a step in the right direction, but we need to see how it successful it turns out and how well they execute on the idea.
CIO Insight magazine wants your worst IT nightmares: here’s a chance to tell the world your personal IT war stories.To fast-track your entry, send it directly to Debra DAgostino at CIO Insight magazine.
IBM is really pushing the packaged services. Here is information from CXOtoday.
Infosys is India’s second largest outsourcing supplier, employing more than 60,000 employees. ComputerWorld described some of the systems and processes the company uses to manage large projects successfully.
Buying the wrong software can significantly affect the health of even the largest company. If you don’t believe me, just ask Christian Streiff, former CEO of Airbus.
Dare Obasanjo, blogger, Microsoft employee, and son of the president of Nigeria (seriously), has assembled a list of five signals that indicate a project may fail: After being at Microsoft for five years, I’ve now begun to see the signs that a project is likely to crash and burn early on. Below is a top five list of signs your software project is in trouble…: Schedule Chicken: This is typically a sign that the project’s schedules are unrealistic.