Root Causes of Troubled Projects

Root Causes of Troubled Projects

For access to this article, please select a purchase option:

Buy chapter PDF
(plus tax if applicable)
Buy Knowledge Pack
10 chapters for $120.00
(plus taxes if applicable)

IET members benefit from discounts to all IET publications and free access to E&T Magazine. If you are an IET member, log in to your account and the discounts will automatically be applied.

Learn more about IET membership 

Recommend Title Publication to library

You must fill out fields marked with: *

Librarian details
Your details
Why are you recommending this title?
Select reason:
Troubled IT Projects: prevention and turnaround — Recommend this title to your library

Thank you

Your recommendation has been sent to your librarian.

There are a number of sources of information on the root causes of troubled projects. These include some notable books on the subject of software risk management, surveys of troubled or 'runaway' projects conducted by management consultants, reports prepared by government accounting watchdogs and internal studies conducted by IT services companies. Root causes which can affect a project during the Project Conception and Project Initiation/Mobilisation stages can be detected during the planning or bid stage of a project. Guidance on how to achieve this is given in Part 2 of this book. If the vendor and the buyer fail to agree that one or more of these root causes is threatening the success of the project and that something needs to be done about it, the vendor can always walk away from the business. Sometimes this brave step does need to be taken. Root causes which can affect a project during the System Design and System Development stages can be detected during project delivery reviews, enabling corrective action to be planned and executed. Guidance on how to achieve this is given in Part 3 of this book. Root causes which can affect a project during the System Implementation and System Operation, Benefit Delivery, Stewardship and Disposal stages can be detected if ongoing project reviews are undertaken throughout the life of the project/system.

Inspec keywords: risk management; software engineering; project management

Other keywords: system operation stages; project mobilisation stages; system development stages; system design stages; disposal stages; benefit delivery stages; system implementation stages; root causes; stewardship stages; project delivery reviews; government accounting watchdogs; project conception; software risk management; IT services companies; project initiation stages; runaway projects; troubled projects

Subjects: Software engineering techniques

Preview this chapter:
Zoom in

Root Causes of Troubled Projects, Page 1 of 2

| /docserver/preview/fulltext/books/pc/pbpc003e/PBPC003E_ch2-1.gif /docserver/preview/fulltext/books/pc/pbpc003e/PBPC003E_ch2-2.gif

Related content

This is a required field
Please enter a valid email address