Here’s a link to the entire paper that will cure the curse of project failure:
- Estimating – either poorly done or rejected. Just amazing how knowledgeable business execs/owners can turn a blind eye to hard data AND then question why the project failed.
- Change Requirements – the typical case of the scope continuing to grow without control and without taking the impact to time/costs into account. I think metal stress was a known test in the 1800’s…200 years later and IT/Business hasn’t found the book.
- Quality – as stated in the doc: defect prevention, defect removal and defect measuring – abc’s of QA.
- Project Tracking – as stated in the doc: Achieving specific and tangible milestones; 2) Expending resources and funds within specific budgeted amounts.
Well next time a project fails don’t go looking for Godzilla tracks, just dig Capers Jones article back up and bang your head against the wall.