Business
12 characteristics of doomed projects
Can you recognize a failing project zombie before it's too late? Although there's no simple or easy answer, the failures do tend to share certain common traits.
Can you recognize a failing project zombie before it's too late? Although there's no simple or easy answer, the failures do tend to share certain traits.
Adapted from Project Smart, here are 12 attributes of bad projects:
- Doesn't meet expectations
- Lacks change management processes
- Lacks project sponsorship
- Insufficient resources or budget are available
- Team doesn't report or escalate critical problems quickly
- No risk planning
- Schedule delays and missed commitments are rampant
- Project is over-budget with no end in sight
- Low morale is a problem
- Uncontrolled scope creep abounds
- Project direction and end-game aren't clear
- Showstoppers haven't been identified
There are a zillion reasons why IT projects collapse, most of which boil down to an ugly set of organizational or political issues. Denial, fear of communicating bad news, and related loveliness are usually the underlying culprits.
If this list describes your project, perhaps it's time to consider serious intervention. If so, read about rescuing software train wrecks.