(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.