TechRepublic : A ZDNet Tech Community

IT Leadership

Host: Toni Bowers
Contact

This is a guest post from Michael Krigsman of TechRepublic’s sister site ZDNet. You can follow Michael on his ZDNet blog IT Project Failures, or subscribe to the RSS feed.

Projects fail for many different reasons, so I took notice when reading a blog post that describes six specific categories of failure. I thought the list worth sharing because it’s a clever way to view the problem.

This list comes hot off the press from the Preventing Project Failure blog (gotta love the title) written by Michiko Diby, Principal at project resolution firm Sealight:

  • Intent Failure - Occurs when the project doesn’t bring enough added value or capability to beat down the obstacles inherent throughout the process. This suggests the original intent of the project was flawed from the beginning.
  • Sponsor Failure - Occurs when the person heading up the project is not actively engaged and/or does not have the authority to make decisions critical to project success.
  • Design and Definition/Scope Failure - Occurs when the scope is not clearly defined, so the project team is unclear on deliverables.
  • Communications Failure - Occurs when communications are infrequent or honest discussion of project problems and issues are avoided.
  • Project Discipline Failure - Occurs when process/project methodology is allowed to lapse so that the mitigation factors inherent in the process are never used.
  • Supplier/Vendor Failure - Occurs when the structure of supplier /vendor relationships doesn’t allow for communication and adjustments.

Categorizing failure by type is an interesting way to bring attention to root causes. Although the list does not break new ground in pinpointing sources of failure, if offers a convenient way to discuss the problem. For a contrasting approach to slicing and dicing causes, see my post 7 fundamentals of IT project success.

Poor communication and mismatched expectations lie at the root of many failures, so we should welcome any serious efforts that raise the profile of these issues. If categorizing failures makes it easier for folks to discuss challenging situations then it’s helpful indeed.

What would you add to the list of failure root causes?

Print/View all Posts Comments on this blog

There are worse things than failure jkameleon@... | 09/30/09
That's an interesting viewpoint Tony Hopkinson | 09/30/09
one more - useless projects viveka | 09/30/09
I can assure you useless projects are Tony Hopkinson | 09/30/09
The Real Issues sutyakk@... | 09/30/09
Another reason for failure MidwestITLady | 09/30/09
More failure reasons. rrickett@... | 09/30/09
Depemds on how good your staff are Tony Hopkinson | 09/30/09
RE: Six types of IT project failure tonycopp@... | 09/30/09
RE: Six types of IT project failure jacob3273@... | 09/30/09
RE: Six types of IT project failure mpries@... | 09/30/09
RE: Six types of IT project failure sharris282828 | 10/29/09
You are mostly correct in your statement TownsendA@... | 11/18/09

What do you think?

White Papers, Webcasts, and Downloads

Recent Entries

TR on Twitter

Archives

TechRepublic Blogs



IT Professional's Guide to Policies and Procedures, Third Ed
Whether you're creating policies for management, training, personnel, support, privacy, Internet/e-mail usage, security, or inventory, you'll meet the needs of your entire enterprise with this one download!
Buy Now
500 Things Every Technology Professional Needs to Know
Did you know Microsoft's RegClean does not work with XP but you can use shareware to clean your registry? Did you know most wireless access points don't have encryption enabled by default? Did you know there are 500 tidbits of information contained in TechRepublic's 500 Things Every Technology Professional Needs to Know that will help you become a successful IT professional.
Buy Now

SmartPlanet

Click Here