Three risk categories that explain it failure

Post Date: Thu, 14 Feb 2008 17:54:12 -0700
A new white paper from Alpha Software describes three broad categories of risk that explain why software projects fail: Process failures arise when a project is "bumped off track," relative to the expected plan. If the goal of a process is to produce a specific outcome, then anything that either delays or prevents the achievement of that specific outcome is a form of process failure. Consider an obvious example of process failure, requirements that are never really (or accurately) determined. This form of failure usually leads to finger pointing between development groups and users, with each claiming the other did not understand. [Other examples of process failure involve:] Communications (including communications latency) Implementing out of date requirements Feature creep (or......
http://feeds.feedburner.com/~r/ZDNetBlogs/~3/23527...
Three risk categories that explain it failure (Abstract text format)
12f1b
Three risk categories that explain IT failure | IT Project Failures
| ZDNet.com
@import url(http://i.zdnet.com/css/v2/base.css);
@import url(http://i.zdnet.com/css/v2/ads.css);
@import url(http://i.zdnet.com/css/v2/blog.css);
On The Insider:
Holy Cleavage!
BNET Business Network:
BNET
TechRepublic
ZDNet
ZDNet
all ZDNet
in Blogs
in News
in Downloads
in Reviews
in Whitepapers
in Dictionary
Go!
Members Log In
Newsletters
Site Assistance
RSS Feeds
Home
News & Blogs
Videos
White Papers
Downloads
Reviews
Popular
IT Project Failures
Michael Krigsman
Get IT Project Failures via:
Mobile
RSS
Email Alerts
Bios:
Michael’s Bio
Pick a blog category
AMR Business Technology Conference 2008
Availability and reliability
Blog annoucements
BOBJSUMMIT08
Book and Blog Reviews
CIO issues
Consulting
Cultural issues
Documentation
Dreamforce 2008
End-user impact
Enterprise 2.0
Enterprise 2.0 Conference
Enterprise2conf
Failure 2.0
Financial impact
Google
Government projects
Implementation
Interview
IT extinction
IT issues
Microsoft
Naked IT
News roundup
Off-topic
Open Source
openworld07
openworld08
Oracle
Packaged Services
Podcast
Politics
Project failures
Project management
Project portfolio management
Project strategy
Project success
Red Herring East 2007
Research and statistics
Risk
SaaS, PaaS, and SOA
Salesforce.com
SAP
SAP TechEd 2008
Sapphire07
Sapphire08
Security and privacy
Short takes
Tools
Training
Uncategorized
Vendor relationships
February 14th, 2008
Three risk categories that explain IT failure
Posted by Michael Krigsman @ 4:54 pm
Categories: Project management, IT issues, Project strategy, Research and statistics
Tags: Software, Information Technology, Failure, Grid, Tools & Techniques, Productivity, Management, Michael Krigsman
A new white paper from Alpha Software describes three broad categories of risk that explain why software projects fail:
Process failures arise when a project is “bumped off track,” relative to the expected plan.
If the goal of a process is to produce a specific outcome, then anything that either delays or prevents the achievement of that specific outcome is a form of process failure. Consider an obvious example of process failure, requirements that are never really (or accurately) determined.
This form of failure usually leads to finger pointing between development groups and users, with each claiming the other did not understand.
[Other examples of process failure involve:]
Communications (including communications latency)
Implementing out of date requirements
Feature creep (or additional features) and its cousin, poorly defined scope
Bugs (defects)
Waiting for someone or something
Partial work
Context switching
Unnecessary processes
Paper shuffling
Unrealistic schedule
Unrealistic budget
Careless, sloppy, or missing software development processes
[T]he presence of one or more of these process failures contribute to business failure if the organization is not able to respond to changing business or market conditions. They also make it difficult to respond to customer-perceived incidents that disrupt service delivery.
Platform failures reflect specific problems with the technology used to develop or deliver software solutions.
The generic term platform applies both to hardware and software individually, and in combination. Some platform failures are also obvious, such as hard disk crashes or network component failure with a corresponding interruption of network traffic. Other examples of platform failure are less obvious, such as when the application does not scale or meet expected levels of performance.Of all the different types of failures, some hardware failures are both the easiest to spot and probably the easiest to anticipate, typically by having spare parts either on-hand or available for just-in-time delivery.
Failures in software platforms (software tools) are more problematic, though they occur frequently enough that they have a name: bugs. It is usually impossible to substitute one software tool for another without a great deal of effort. This becomes particularly onerous if the bug is in a critical tool, and the vendor (or in-house developer) cannot quickly provide either a fix or work-around.
There are also platform failures that can be less obvious to spot, specifically getting close to boundary conditions of the hardware or software including network capacity, balance between physical RAM and swap file, getting close to hard disk space limits, etc.
Business failures refer to issues and problems driven by the internal organization itself.
One of the most obvious forms of business failure also turns out to be the primary reason that development organizations cannot readily adapt to changing conditions: specifically, lack of management commitment. No project can succeed without management commitment (and on occasion, management drive).
[E]xperience [also] suggests an expansion of the concept of business failure to include the notion of tool vendor concerns for the customer value chain. The customer of my customer should be treated like they are my customer. Does the tool vendor do that?
THE PROJECT FAILURES ANALYSIS
The white paper places the risk sources underlying IT failure into three reasonable categories. Nonetheless, for simplicity’s sake, I recommend readers combine business and process failures into a single category encompassing both. Importantly, the paper does a good job making the distinction between business and technical causes of failure, and it provides examples of each.
Although the white paper covers no new ground in categorizing project risk, it includes a useful chart showing “the relationship between complexity, calendar duration, and risk:”
Take a project task, such as developing a particular feature, and map it onto the chart. The grid provides a quick litmus test for evaluating estimates against a consistent framework of risk, complexity, and time. It’s a simple, nice, and useful method to perform intuitive risk testing.
Overall, the white paper is worth a read. It won’t send off skyrockets in your mind but it’s solid, covers good territory, and provides lots of concrete examples.
Michael Krigsman is CEO of Asuret, Inc., a software and consulting company dedicated to reducing software implementation failures. Click here to discuss this post with him on Twitter.
See his full profile and disclosure of his industry affiliations.
« Previous postNext post »
Talkback
Most Recent of 13 Talkback(s)
Thread View
Flat View
RE: Three risk categories that explain IT failure
Interesting responses to this post. In regard to your comment, "Nonetheless, for simplicity’s sake, I recommend readers combine business and process failures into a single category encompassing both... (Read the rest)
Posted by: Steve Romero Posted on: 02/20/08
You are currently:
Logged In as: a Guest | Login | Terms of Use
Wow...
jasonp@... | 02/15/08
Why do some folks thing IT is somehow different?
No_Ax_to_Grind | 02/15/08
Give me a break
mkrigsman@... | 02/15/08
You missed the point completely. (or didn't like hearing it)
No_Ax_to_Grind | 02/15/08
Problem is deeper than project management alone
mkrigsman@... | 02/15/08
Actually, that is part of GOOD project management.
No_Ax_to_Grind | 02/15/08
No ax is totally right
stevey_d | 02/16/08
Because IT projects are different to other projects
Fred Fredrickson | 02/17/08
RE: Three risk categories that explain IT failure
ukdbmsone | 02/15/08
Better choice.
No_Ax_to_Grind | 02/15/08
No, just one choice
Fred Fredrickson | 02/17/08
People in glass houses ...
alphaflack@... | 02/15/08
RE: Three risk categories that explain IT failure
Steve Romero | 02/20/08
What do you think?
Subject (max length: 75):
Reply:
5 Trackbacks
The URI to TrackBack this entry is:
http://blogs.zdnet.com/projectfailures/wp-trackback.ph p?p=598
links for 2008-02-15
(tags: e-gov) Three risk categories that explain IT failure | IT Project Failures | ZDNet.com (tags: **** risk process) Trackback by Anonymous — February 15, 2008 @ 3:32 am
Michael Krigsman picks up our "risk" white paper
One of the most rewarding blogs on the Web has picked up our recently issued white paper. Too much IT coverage fawns over new (and untested) gee-whiz products, repurposed case studies (served up by vendors), industry issues that are ... Trackback by Alpha Software — February 15, 2008 @ 4:25 pm
One Year In A IT Project - Day 12
Day12b. See Michael Krigsmans posts about a Three risk categories that explain IT failure. Trackback by Geek And Poke — February 16, 2008 @ 7:34 pm
One Year In A IT Project - Day 12
See Michael Krigsmans posts about a Three risk categories that explain IT failure Originally posted on: geekandpoke.typepad.com/geekandpoke/200... Trackback by Anonymous — February 18, 2008 @ 3:35 am
links for 2008-02-22
Three risk categories that explain IT failure Trackback by Anonymous — February 23, 2008 @ 3:29 am
SponsoredWhite Papers, Webcasts, and Downloads
Desktop Virtualization for the Enterprise RingCube
Building a Small Office Network: Getting Started Cisco Systems
Learn What VoIP Can Do for You Cisco Systems
Recent Entries
Five strategies for 2009 IT gold
Select Comfort: home-grown IT failure
CIO strategy: 10 qualities of IT greatness
A reader’s ZDNet holiday poem
IT failure and holiday cheer
Top Rated
Select Comfort: home-grown IT failure+18 votesRequirements and failure: Interview with CA's SVP of IT Governance+16 votesStudy: 68 percent of IT projects fail+15 votesUniv. of Wisconsin CIO discusses IT failure [podcast]+11 votesIT failures town hall: Jan 7 (via phone conference)+9 votesUK Transportation Department IT failure: 'Stupendous incompetence'+8 votesCIO strategic competencies for 2009+7 votesIT ethics and the recession+7 votes
Follow ZDNet on Twitter
Archives
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
All "IT Project Failures" talkbacks
ZDNet Blogs
A Developer's View
All About Microsoft
The Apple Core
Between the Lines
BriefingsDirect
Collaboration 2.0
Community, Incorporated
CRM 2.0: The Conversation
Dev Connection
Digital Cameras
Ed Bott's Microsoft Report
Emerging Tech
Enterprise Alley
Enterprise Web 2.0
Feeds
Forrester Research
Googling Google
GreenTech Pastures
Hardware 2.0
Home Theater
iGeneration
Irregular Enterprise
IT Facts
The IT Grind
IT Project Failures
Laptops & Desktops
Lawgarithms
Linux and Open Source
Managing L'unix
The Mobile Gadgeteer
On Sustainability
Rational Rants
The Semantic Web
Service Oriented
Smartphones and Cell Phones
Software & Services Safari
Software as Services
SOHO Networking
Storage Bits
Team Think
Tech Broiler
Tom Foremski: IMHO
The ToyBox
The Universal Desktop
Virtually Speaking
The Web Life
ZDNet Education
ZDNet Government
ZDNet Healthcare
Zero Day
SponsoredWhite Papers, Webcasts, and Downloads
Desktop Virtualization for the Enterprise RingCube
Learn What VoIP Can Do for You Cisco Systems
Is power your weakest link in data center flexibility? Key considerations for power systems in adaptive IT environments Eaton Corp.
CIO Sessions
Check out our video interviews with leading CIOs today!
What it takes to stay on the edge of innovation
PARC VP, hardware systems laboratory: Scott Elrod
12:38
Going green and managing costs during tough economic times
State of California CIO: Teri Takai
10:28
Taking chances with the core brand
Mozilla CTO: Brendan Eich
10:38
Transforming the company and developing new delivery platforms
Netflix Chief Product Officer: Neil Hunt
11:25
All CIO Sessions »
Blogs
All About Microsoft
The Apple Core
Between The Lines
Googling Google
Digital Cameras
Hardware 2.0
Laptops and Desktops
SOHO Networking
Storage Bits
Zero Day
Product Reviews
Home Theater
PCs, Software and Peripherals
Smartphone and Cell Phones
Digital Cameras
Videos
CIO Vision Series
At The Whiteboard
News Video
White Papers and Webcasts
Business Management
Career Development
Infrastructure Management
ManageMobile - Wireless Communications
Network Security
Webcasts
Downloads
Internet Tools and Utilities
Spyware Removers
System Optimizers and Diagnostics
System Utilities
More
2008 Holiday Gift Guide
Photo Galleries
Latest News & Blogs
Podcasts
Site Index
ZDNet
ZDNet News & Blogs
Hardware,
IT Management,
Networking,
Operating Systems,
Photo Galleries,
Security,
Software,
Web Technology,
All News,
Dev Connection,
Emerging Technology,
Enterprise Alley,
Googling Google,
GreenTech Pastures,
IT Project Failures,
Linux and Open Source,
Managing Linux,
The Social Web,
Storage Bits,
Virtually Speaking,
The Web Life,
Podcasts
Product Reviews
A/V Receivers,
Cell Phones & Accessories,
Desktop Monitors,
Desktops,
Digital Cameras,
Digital Camcorders,
Flat-panel TVs,
Laptops,
Portable Video Players (PVPs),
PDAs,
Smartphones,
Software,
Storage
Product Blogs
The Toybox,
Digital Cameras,
Laptops and Desktops,
Mobile Gadgeteer,
SOHO Networking,
Smartphones and Cell Phones,
Home Theater
White Papers & Webcasts
Cost Control / Risk Management,
Customer Support Services,
IT HR / Staffing / Training,
Resources Management,
Strategic Planning,
Webcasts
Downloads
Antivirus Software,
File and Disk Management Utilities,
Image Editing,
Privacy Software,
Shell and Desktop Management Enhancements
Site Help & Feedback
Site Map
Popular on CBS sites: CES | Spore | iPhone 3G | Katy Perry | Antivirus Software | GPS | Recipes | Macworld | NFL
BNET | CBS College Sports | CBS Radio | CBS.com | CBSNews.com | CBSSports.com | CHOW | CNET | CNET Content Solutions | GameSpot | International | Last.fm | MaxPreps | Metacritic.com | Moblogic | MP3.com | mySimon | NCAA | Search.com | Shopper.com | TechRepublic | The Insider | TV.com | UrbanBaby.com | UWIRE | Wallstrip | ZDNet
About CBS Interactive |
Jobs |
Advertise
© 2009 CBS Interactive Inc. All rights reserved. |
Privacy Policy |
Terms of Use
0
|