Troubled Projects

Just completed a training course on rapid assessment and recovery of troubled projects. Even though I am a seasoned project manager and have dealt with a few problem projects, the course was excellent and provided me with a structured methodology and tools for dealing with such types of projects. The main theme wasn't rocket science and covered the usual key steps of agreeing the scope (The Charter), planning the assessment phase, carrying out an assessment, planning the recovery, and carrying out the recovery. Inside these phases were plenty of tools, methods and suggestions for the detail work required.
Of course one theme was not getting into trouble in the first place and the usual suspects were all there. I have listed some of them: -
· Lack of job/role/responsibility definitions
· Lack of correct skills
· Lack of sponsor or stakeholder buy in
· Lack of user involvement
· Optimistic schedules
· No or poor risk management
· Poor planning
· Bad design
· Poor or no controls
· Missing tasks
· Scope creep or unrealistic requirements (Gold plating)
· Switching sub contractors or key products during project
Obvious really but human nature being what it is problem projects will stir occur, therefore the more pre-planning you can do coupled with key reviews during the project are sure to help.
You do still see very high statistics quoted, particularly in IT, on how many projects fail although you wonder on the criteria. I could sometimes argue that a project being re base-lined due to a reassessment of completion times is not necessarily a failure but statistically may be counted as such.
The bottom line is use a methodology, train your people, get a sponsor and ensure frequent reviews. Well that’s my view.