"Remaining work" report

Hi!

I would like to know why the "Remaining work" report in the latest Beta 3 edition is different than it was in the Beta 2?

In the current Beta 3 the input values are “Iteration”, “Area”, “Work Item Type”, “Start Date” and “End Date”. The biggest value for “End Date” can only be the actual date.

The example included in the MSF process guidance on the Project Portal, on the other hand, shows the “old” report, as it was in the Beta 2. On this report, the input values are “Iteration”, “Area”, “Work Item Type” and “Trendlines”. The result shows the prediction of the end date for the project, by extrapolating the areas of active, resolved and closed scenarios. It seems that this report is not restricted by a time range.


My questions are:

1) Why is the biggest value for “End Date” the actual date? Can this be changed?

2) Where have the trendlines gone?

3) I am working with a small project with just a few scenarios and tasks. Is this enough data?

4) Is there any other report that shows the prediction of the end date for the project, as this report showed in Beta 2?

Thanks,

Ana

[3314 byte] By [AnneR] at [2007-12-17]
# 1

Hi, AnneR

Unfortunately, we have had to cut the trendlines from this report. For the RTM version, you can specify dates > today as the end date via a parameter, which now uses the new Reporting Services date control.

Predictive reporting is not something that we are including in our OOB reports for V1.
1) Why is the biggest value for “End Date” the actual date? Can this be changed?

2) Where have the trendlines gone?

3) I am working with a small project with just a few scenarios and tasks. Is this enough data?

4) Is there any other report that shows the prediction of the end date for the project, as this report showed in Beta 2?

TomPatton at 2007-9-9 > top of Msdn Tech,Visual Studio Team System,Team Foundation Server - General...

Visual Studio Team System

Site Classified