What Are The Root Causes of Project Problems and Failure?

4) Project Definition

Project definition includes objectives, scope and requirements.  One of the most common root causes of project problems is the lack of a clear and complete written definition.  Without clear and written objectives, stakeholders will drift apart in their understandings of the project-stated end results.  As the project progresses, it is likely some of the stakeholders will not agree that the project is on track to meeting its objectives and deem it to be a partial, if not a complete, failure.  Without a clearly written statement detailing what is in and out of scope, projects are at risk of “never ending.”  Management and other stakeholders are likely to continue adding scope or may become frustrated as they see “unnecessary” scope added by others, delaying the completion of the project. 

Even with clearly defined objectives and scope, a project with no or limited detail requirements is also highly likely to fail.  It is imperative that the stakeholders go through the requirements-gathering process to achieve two objectives:  First, the process will ensure that what is to be built is clearly and accurately defined, down to the smallest details that the stakeholders care about.  Second, the process ensures that the stakeholders discuss, negotiate and eventually agree on what is to be built so there is no argument once design and development activities are started and completed.  There is alignment – a key ingredient to a successful project. 

Mitigating the risk of project failure due to poor definition requires a clear delineation and documentation of the projects’ objectives, scope and requirements.

Project situations that display symptoms of a lack of project definition include: