A blog to offer ideas, suggestions and techniques to turn around or fix troubled or failed IT projects

<< Don't Let This Be the Life Cycle of Your Project A Checklist for Assessing Some Important Areas of Project Risk >>

9 Causes for Failed Projects

by Mark Davison January 31. 2011 21:14

9. Lack of control/change process
8. Insufficient or no risk planning
7. Unrealistic budgets
6. Undefined project success/closure criteria
5. Lack of stakeholder buy-in
4. Poor project requirements
3. Unrealistic schedules
2. Insufficient resource planning
1. Poor communcations

Tags:

A Checklist for the Manager Who Fixes Troubled Projects1. Identify the "fix it" target(s) - those areas or activities that need to be changed2. ...You Can Win At Office PoliticsPolitics is a business fact of life – learn to play it well by refining the ways in which you ...Welcome to the FixMyProject Blog!This blog will offer information about ideas, suggestions and techniques to turn around or fix troub...

Add comment

Name*
E-mail*
Website
Country Country flag

b i u quote

Comment
Preview

Notify me when new comments are added

5+5 =

ATLANTA - CHICAGO - DETROIT

Acquisition Due Diligence and Integration	IT Strategy
Acquisition Integration and Carve Out Leadership	Complex Business Change and Program Management
Business Operations Improvement	Sourcing Strategy and Vendor Management
Cost Optimization	IT Effectiveness
Interim CXO

9 Causes for Failed Projects

About Mark Davison

Month List

RecentPosts

9 Causes for Failed Projects

About Mark Davison

Month List

Newsletter

Thank you

Tag cloud

RecentPosts