1. Why Projects Fail
From: Successful Project Delivery:, David Yardley, Addison-Wesley, 2002
Rapid Development, Steve McConnell, Microsoft Press, 1996
Technology-Related Mistakes
Lure of leading edge (bleeding edge) technologies
Technical solution to non-technical problem
Technology-led development
Dependence on software packages to satisfy requirements
Lack of tools throughout the development cycle
Silver-bullet syndrome
Overestimated savings from new tools or methods
Switching tools in the middle of a project
Lack of automated source-code control
People-Related Mistakes
Lack of effective project sponsorship
Lack of stakeholder buy-in (sponsor, team leader/members, end users, marketing dept.)
Lack of user input
Politics over substance
Uncontrolled problem employees
Heroics
Adding people to a late project
Noisy, crowded offices
Friction between developers and end users (customers)
Unrealistic expectations
Resistance to change
Hostile organizational structure
Inexperienced Project Manager
Lack of business justification
Unclear or ambiguous business priorities
Lack of User Training
Process-Related Mistakes
Absence of any project methodologies
Wasted time during the fuzzy front end
Failure to identify and mitigate project risks
Lack of user input
Requirements – too many features
Feature Creep
Omitting necessary tasks from estimates
Insufficient management controls

2. Lengthy project time schedules
Insufficient testing
Testing not timely
Overly optimistic schedules
Insufficient planning
Abandonment of planning under pressure
Inadequate design
Shortchanged quality assurance
Planning to catch up later
Compiled by Ron Watson
*****************************************
****************************************