7 Characteristics of Dysfunctional Software Projects

October 7, 2008 · Filed Under Project Management, Thoughts  - 0 Comment(s)

From Mike Evans, Coauthor of my book on Software Sizing, and Risk Management while studying over 350 projects:

  1. Failure to Apply Essential Project Management Practices
  2. Unwarranted Optimism and Unrealistic Management Expectations
  3. Failure to Implement Effective Software Processes
  4. Premature Victory Declarations
  5. Lack of Program Management Leadership
  6. Untimely Decision-Making
  7. Lack of Proactive Risk Management



Thank you for reading “Dan on Estimating”, if you would like more information about Galorath’s estimation models, please visit our contact page or call us at +1 310 414-3222.

Related posts:

  1. Why Projects Fail From A Technical and Process Viewpoint There was an interesting article in SDtimes  The article claims that “Most cases of failure that I have seen have...
  2. Eight Causes of Project Failures: UK Government IT Projects From the POST report on UK Government IT projects, there are some insightful lessons on why projects fail. Now if...
  3. Risk On IT Infrastructure Projects Identifying the risk on IT infrastructure projects is a key to viable cost & schedule analysis.  While working on risk...
  4. Government IT Projects: Opportunity For More Success I heard of a wonderful blog on Zdnet regarding additional oversight and transparency in Government IT projects costs, schedule: S.920...
  5. Estimation Plus Process and Measurement Rigor Yields More Successful Projects: SEER and Tracer It has been rewarding working with the Computer Aid  (CAI) people, the people who sponsor the ITMPI in tying together...

Comments

Leave a Reply




CommentLuv badge