Failure rates of software and IT projects are abysmal. Industry studies reveal that only 1 out of 5 software projects is likely to bring full satisfaction. Project reviews keep identifying the usual suspects of poor communication, underestimation, and scope creep as the cause for failure. Typically these problems are symptoms, and not root causes.
This presentation addresses the unique characteristics of software project management, with a particular focus on the people and process issues that must be managed.
This presentation was given at the PMI SF-BayArea Chapter meeting January 20th, 2010 in Walnut Creek, CA.
Download here –> 7 Signs of a bad project estimate
Tags: best practices in project estimating, business case for process improvement, CMMI, cost and schedule overruns, defect metrics, disaster projects, estimating, estimating large projects, gopal kapur, how to estimate, joe kolinger, project management estimating, project rescue, QSM, SLIM, software estimate