Forecasting based on rolling averages
![]()
(This was originally sent as an email to Benjamin Chodroff on October 12, 2011)
1) We need a 3 point rolling average of team velocity, and have this information expressed as a chart of average team velocity over time. The three points used for the average are the three most recently completed sprints. Team velocity is to be calculated in Story Points / Sprint. 2) Need to forecast a release completion date based on rolling velocity. As a sprint within a release is completed, the forecast is updated based on the updated rolling velocity. The forecast would look like a burn-down chart, with a forecast line intersecting the time axis at the date all the story points are projected to be completed. 3) With regard to time tracking, we want to enter resource availability, and then show for each sprint how many stories were burned down per unit time. Task estimation in hours is discouraged and burn-down in hours per sprint will not be used. 4) Story point burn up is of interest, with several line graphs- one per state. |
One answer
![]()
This response came from James Moody:
1) This sounds like it might be a modification of the team velocity report, which is has a bar chart plotting completed story points per iteration. 2) Advanced Release Burndown sounds applicable here. 3) So you're talking about how many stories, rather than the number of story points? This sounds like you want something like team velocity, except to count number of stories rather than number of story points. (From your description it sounds like you want multiple sprints represented in the report, with (say) one bar or data point per sprint - if that's not the case, let me know). 4) We have a report called "Story Points". You could modify this so that it included only closed (completed) story points in a line chart instead of open + closed in an area chart. |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.