Project velocity report: zero resolve rate, why?
This report looks like it might be useful to me. Alas alack I find no documentation for it in the help anywhere. EVen on the MSDN pages (http://msdn2.microsoft.com/en-us/vstudio/aa700949.aspx) it's not described (there's a link from it's entry to the Bugs by Priority report help page (a clear bug in the help system).
I don't know how to interpret this and to have any faith in it need a low down. I see immediately when I run it that line for Resolved flatlines at zero (in spite of plenty of tasks being closed as complete in this time frame on my project). WHat does this measure, why is it broken and how can I fix it?
Beneath is a table which has great transition data (I'd love to have this on hand) ut looks similarly completely wrong. It lists a pile of iterations which are from last year and have no activity in the time frame of the report (the last month) and doesn't list any activity in the iterations that ran this last month.
How do I diagnose what's up here, and establish some understanding of, confidence and faith in this report?
All help appreciated.
Bernd.
Hi,
to your first aspect: You can find a documentation for each report on the 'Process Guidance' site.
To get there, just click in your Sharepoint Team Project Portal site on the Process Guidance link on the left.
On the PG site click on the 'Index-Tab' above and then select 'Reports' on the left.
(or simply type: http://[TF-Server]/sites/[ProjectName]/Process%20Guidance/Supporting%20Files/ReportsIndex.htm )
(I only use the Template for CMMI Process Improvement, so I don't know if there is the Process Guidance site when you're using the Agile-Template )
So that's all I know, perhaps it helps you a little bit 
Good Luck
Alas, the documentation in the Process Guidance is poor to say the least. It states obviosu things like this:
| Resolved Work Items | - This line shows the count of work items resolved on each day.
|
without letting me know what "resolved" means. You see we have a highly adapted workflow (state transitions) on our template. Based on Agile but we grafted on what we use on other projects on legacy systems. Namely that any work item has state transitions that in the simplest sequence run something like this:
Proposed
Approved
Active
Testing
Documentation
Closed
Resolved to me is context specific for starters but in the broadest sense means enter the Closed state.
It wouldn't surprse me if changes to our template broke this report (hence velocity is zero) but what I'd appreciate is some way of learning how, why and how to fix it and have found googling around and the MS help system to be less than fruitful for now (time consuming without progress).
Bernd:
You should be able to alter the report def file (.rdl) and change
[Work Item].[System_State].[System_State].[Resolved]
to
[Work Item].[System_State].[System_State].[Closed]
You will then want to chage the chart to plot [Closed] instead of [Resolved]
