tag:blogger.com,1999:blog-3451061530279218402.post2442515668730707241..comments2023-07-05T11:29:39.669-05:00Comments on Stoz Studios: Evidence-Based Scheduling: Seth Coster StyleSeth Costerhttp://www.blogger.com/profile/14593463506257818030noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-3451061530279218402.post-88612781702007371182010-12-06T02:22:28.025-06:002010-12-06T02:22:28.025-06:00This is goddamn awesome. And I read the joel post....This is goddamn awesome. And I read the joel post. GOING TO BUILD ONE OF THESE TOMORROW WHEN MY AWAKE-VELOCITY IS HIGHER.Samuel 'Sqm' Costerhttps://www.blogger.com/profile/04247946341433154363noreply@blogger.comtag:blogger.com,1999:blog-3451061530279218402.post-33793123805268993412010-11-30T08:24:02.728-06:002010-11-30T08:24:02.728-06:00Weighting shouldn't make much of a difference ...Weighting shouldn't make much of a difference in a large project. If you have a project which is comprised of 100 tasks (which is certainly a reasonable number), totaling 500 hours, and one of your tasks is 10 hours and one is 1 hour, by the time you get 20-30 of those tasks under your belt, the weights would have a negligible effect. The purpose of the velocity variable is to show how accurate you are in proportion to the size of the task, which it does. For example, if you are off by 30 minutes on a 10 hour estimate, you were pretty close, and your velocity reflects that. If you were off by 30 minutes on a 1 hour estimate, you were way off, and your velocity reflects that as well.<br /><br />I'm not quite sure what you mean by basing it on the sum of each column.<br /><br />And as far as adjusting future estimates, if you feel that there are past velocities which are outliers, you can just delete them and they won't be used in computing the average.Seth Costerhttps://www.blogger.com/profile/14593463506257818030noreply@blogger.comtag:blogger.com,1999:blog-3451061530279218402.post-53533113684779258902010-11-29T23:05:18.765-06:002010-11-29T23:05:18.765-06:00I have one concern: WEIGHTING!
If you are a half ...I have one concern: WEIGHTING!<br /><br />If you are a half hour off on a 1hr estimate, the effect is relatively large. If you are half hour off on a 10hr estimate, the effect is relatively small. What if your average velocity was based on the sum of each column instead of the average of the velocities?<br /><br />And I just thought of something else. What if you were to adjust your estimates based on your previous ones, since the work you put in at the beginning of a large project may totally change the downstream work required. But your re-estimates would be better informed and so your velocity-scaling based on the previous work would be wrong.Anonymousnoreply@blogger.com