Troubled IT Projects: Prevention and Turnarounds

Table 4.1 shows the root causes of troubled projects which are detectable and preventable at the planning or bid stage.
| Chapter | Preventable Troubled Project Root Causes |
|---|---|
| 5 Opportunity | RC03 Project based on state-of-the-art and immature technology RC05 Buyer s funding and/or timescale expectations unrealistically low RC06 Buyer failure to break a complex project into phases or smaller projects RC08 Buyer failure to define and document requirements (functional and non-functional) RC17 Full-scope, fixed-price contracting (requirements, design and development) |
| 6 Engaging the Potential Buyer | RC01 Project based on an unsound premise or an unrealistic business case RC02 Buyer failure to define clear project objectives, anticipated benefits and success criteria RC04 Lack of Buyer Board-level ownership/commitment or competence RC09 Failure to achieve an open, robust and equitable Buyer-Vendor relationship RC11 Buyer lack of sufficient involvement of eventual end-users |
| 7 Shaping the Solution | RC03 Project based on state-of-the-art and immature technology RC19 Poor choice of technical platform and/or architecture RC21 Poor choice of design/development method |
| 8 Defining the Solution | RC13 Vendor failure to define project tasks, deliverables and acceptance processes RC26 Buyer retains design authority with right to approve/reject low-level designs |
| 9 Project Estimating and Planning | RC12 Vendor underestimation of resources (predominantly person-effort) required RC15 Poor project planning, management and execution RC16 Failure to clearly define roles and responsibilities in the contract/subcontracts |
| 10 Quality Assurance and Risk Management | RC01 Project based on an unsound premise or an unrealistic... |