It Happens... There are many reasons why a project can get off track. Some explanations for project failure include a lack of organizational inertia, project complexity, and/or lack of clarity or purpose.
In How to Spot a Failing Project, Rick Cook finds that 35% of IT projects were successful, whereas 19% failed. The remaining 46% delivered a useful product but suffered from budget overruns, prolonged timelines, and application feature shortfalls.
E&A is often consulted on how to get a project back on track. Our research has found that by taking a step back and walking through the eight steps explained in our publication, the project can be redirected and put back on course:
View our publication for more information and insight.