3 ms·
This may just be cynicism, but since you assign point values to the work it seems like there would be a general downward trending as you get more into the proje
by skolor 18y ago
This may just be cynicism, but since you assign point values to the work it seems like there would be a general downward trending as you get more into the project. I know at the start of any project I largely undervalue the difficulty of implementing a feature or fixing a bug.
Similarly, it seems that there is a large spike in point values right after showing the project to someone else. I know that, again, in my experience, after showing my projects off I tend to far over value the difficulty of new features. Typically that's because I end up spending 75% of the time leading directly to that showing off a project is to fix all the bugs and make it stable. After I've spent a long time fixing bugs, I start adding the difficulty of fixing the bugs that will come out of the feature to the difficulty of the implementing the feature. After a little while I stop doing that, and the difficulty would go down for the same feature.
Not saying anything about the post, or the quality of work done. I was just pointing out my observations on some of the statistical foibles.
- gaborcselle 18y agoGood observations. General downward trending: That's been the case with us. If I went back and corrected the first few weeks of points, I would probably assign more points to the individual tasks, moving up the first few weeks of values. Yet I tend to correct the number of points assigned to each item before I mark it as "finished", thus somewhat normalizing the value of each point. Large spike in point values: Nah, what actually happened is that we filed many more small (1-point) bugs, rather than overestimating values of new bugs and features. Thus, after showing off the new versions and handing out alphas, we'd have more work items at smaller valuations.
- miss_garrison 18y agoDid you assign points to bugs and chores, as well? Just curious, because Pivotal suggests not to count bugs towards the velocity of the project, because bugs are not directly bringing business value... Just curious about your approach.