tag:blogger.com,1999:blog-20646966.post7780159685299716721..comments2007-10-15T13:36:20.638-07:00Brucehttp://www.blogger.com/profile/17924943461128606986noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-20646966.post-740425779559543082007-10-15T13:36:00.000-07:002007-10-15T13:36:00.000-07:00There's a <A HREF="http://blog.brodzinski.com/2007/10/software-product-success-stories.html" REL="nofollow">meme about successful projects</A>. I'd like to invite you to join.Pawel Brodzinskihttp://www.blogger.com/profile/04369257211504152485noreply@blogger.comtag:blogger.com,1999:blog-20646966.post-2350821434323470562007-09-29T14:28:00.000-07:002007-09-29T14:28:00.000-07:00Giving a range of dates is one approach to estimating effort. Adding chance to time estimate is another. Anyway estimates are always connected with some risks. The more aware of those risks the person is the better estimates she will bring.<BR/><BR/>The issue with MS Project schedules should be resolved with putting pessimistic options into the schedule. As far as you can have the realistic schedule of course, which isn't so obvious.<BR/><BR/>By the way: I'd like to see salespeople with estimates varying by 400% (4 versus 20 weeks).Pawel Brodzinskihttp://blog.brodzinski.comnoreply@blogger.comtag:blogger.com,1999:blog-20646966.post-70151844615540584042007-09-21T03:24:00.000-07:002007-09-21T03:24:00.000-07:00Can I read between the lines here that LiquidPlanner will allow you to enter estimates as ranges? And perhaps allow you to break down and refine these estimates throughout the project so that you can derive an expected completion date with a defined level of certainty?David Dalyhttp://outofthetriangle.wordpress.com/noreply@blogger.com