tag:blogger.com,1999:blog-5879803756523278249.post8367519938406862922..comments2012-03-17T10:58:49.475+00:00Comments on Gary Thompson. Random thoughts.: Project estimation (duration, effort) and Project FailureGary Thompsonhttp://www.blogger.com/profile/14014271482571618258noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-5879803756523278249.post-83582650540877814362008-04-18T09:51:00.000+01:002008-04-18T09:51:00.000+01:00Tom, I agree that a project that is over estimated...Tom, I agree that a project that is over estimated can be a failure. I have a general rule that a project that is 20% under or over budget has been well run (to be honest 20% still isn't great). But an overestimated project that is delivered earlier has less of an impact, unless the organisation is really fine tuned, and most are not.<BR/><BR/><A HREF="http://www.softwaremag.com/archive/2001feb/CollaborativeMgt.html" REL="nofollow">Collaborating on Project Success</A> Provides a good description of success criteria.Gary Thompsonhttps://www.blogger.com/profile/14014271482571618258noreply@blogger.comtag:blogger.com,1999:blog-5879803756523278249.post-41948485348129357262008-04-18T00:11:00.000+01:002008-04-18T00:11:00.000+01:00You describe a project failure as one that has bee...You describe a project failure as one that has been underestimated in terms of money and time Gary, but what about the rare occasions where a project is overestimated? Where it comes in way earlier than predicted? At what point do you define a project a failure? Particularly an internal one, I suppose an overestimated external project is almost always a success as long as the client is happy.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-5879803756523278249.post-28091960674034847872008-04-17T23:04:00.000+01:002008-04-17T23:04:00.000+01:00you might also want to visit this site about emplo...you might also want to visit this <A HREF="http://www.macdataadvantage.com" REL="nofollow">site</A> about employee backgroundAnonymousnoreply@blogger.com