progress tracking time vs story points - complexity attribute for planning

 0 Natalia Liaskovski (57●1●12●19) | asked May 12 '13, 12:46 p.m. We have Story work items that represent new functionality and sized up by the story points. We also have other work that does not amount to new functionality or user stories. That work is represented by tasks, defects, other various work item types, none of which have story points attribute. The universal denominator across all work items is time (estimated, spent, corrected, etc. ) The issue is the planning  complexity attribute, which seems to be mutually exclusive. Ideally one would like to see percentile of progress on the plans as it relates to all work - new functionality and non-new functionality related, in other words: overall progress. The solution seems easy enough - just to set complexity to time. However, in that scenario setting story points to track progress is irrelevant - none of the story points translate to time. (then what's the point of having them?) In order to track progress across stories one would have to set time estimates on stories in addition to story points - there is no built-in formula that would translate points to time nor there is a way to provide it (or is there ?).  Which makes story points kind of useless for progress tracking ... On the other hand , if we set complexity attribute to Story points - all other work that does not have story points has no way of progress tracking. In that scenario - everything must be a Story, in order to track progress on plans. In addition to that, if progress is measured in Story points, all stories have to be broken down into 1 iteration duration - how else would you show that your Story has 3 ot 5 points complete ? All in all in order to have a usable progress tracking in plans for both point based and time based progress, there has to be a way to define how to: 1) translate points to time so that we can see progress on all work - story and non-story related 2) a 'story points completed' attribute that would be taken into that formula Is there a way to have it done in CLM 3.x or 4.x ?