Michael Krigsman

Michael Krigsman is recognized internationally as an analyst, strategy advisor, enterprise advocate, and blogger. Interact with Michael on Twitter at @mkrigsman.

Latest Posts

Eight Causes of IT Project Failure

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.

December 7, 2006 by


Government Report: UK IT Projects Still Failing

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.

December 4, 2006 by


Packaged Services in ERP

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.

October 25, 2006 by


Five Signs of a Doomed Project

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.

October 19, 2006 by