The Top Ten Reasons Projects Fail (Part 9)

Home  >  Articles  > 
The Top Ten Reasons Projects Fail (Part 9)

Frank Winters

November 5, 2003






This entry in the failure series is a follow-up to Part 8 regarding estimation. The topic deserves more thought and discussion, and I've had several comments regarding Part 8, so here's some more about estimation.

What is an appropriate confidence level?

Many believe that estimates with high confidence levels--I recommend striving for 95 percent -- are much more costly than those with lower confidence levels. So much more so that it just doesn't pay to routinely strive for 95 percent confidence.

 

A reviewer of part 8 likes to try for 80 percent. He feels that if estimates are consistently at 80 percent, a team should expect to miss the targets one time in five--a much better than average success rate, he said.



Please login/register to read the entire article.





sponsored announcements and special offers
Difficult for competitors to equal. EMA reviews IBM Rational's new quality & requirements management offerings. The verdict, "For companies seeking to improve ROI delivered by software projects,we believe Rational's value proposition is difficult to match."

Microsoft Project Conference 2000
Exclusively disclosing the powerful capabilities included in Microsoft Project 2010 and Microsoft Enterprise Project Management (EPM) Solutions while providing real world guidance on how Microsoft Project 2007 and Microsoft EPM Solutions are helping customers today with project and portfolio management to save money, enhance efficiency and prepare for future growth. Register Today!

Use WorkLenz PPM to Manage Agile Software Development
We invite you to download Métier’s latest white paper, Agile Software Development with WorkLenz, to learn how you can use WorkLenz to manage agile within your organization.



"If you think you can, you can. And if you think you can't, you're right."
- Mary Kay Ash