Reports
Hi,
I have some questions about the reports. I am using RTC 2.0.
Is there some doc online on the reports?
Release burndown
We did not use the story points when we did the project. It was a small project in a class setting.
If we add the story points at this point (now) for each story will we able to see the release burndown?
Will I then be able to see the team velocity?
Repository metrics
I would like to see the metrics between specific dates. Is that possible? Is com.ibm.team.repository the namespace for the Java projects created by users? Can we go into looking a particular Java projects?
Thanks,
Christelle
I have some questions about the reports. I am using RTC 2.0.
Is there some doc online on the reports?
Release burndown
We did not use the story points when we did the project. It was a small project in a class setting.
If we add the story points at this point (now) for each story will we able to see the release burndown?
Will I then be able to see the team velocity?
Repository metrics
I would like to see the metrics between specific dates. Is that possible? Is com.ibm.team.repository the namespace for the Java projects created by users? Can we go into looking a particular Java projects?
Thanks,
Christelle
3 answers
On 2/20/2010 4:37 PM, scharffc wrote:
The release burndown is designed to work on story points, so if you add
a story points attribute to your work items, and ensure that this
attribute is set as a "top-level work item type" (you can do this in the
project area editor), the release burndown should work. Note that the
release burndown is a view across multiple iterations throughout a
release, with one data point per iteration. Sounds like what you really
want is the regular burndown chart, no? It operations on the "estimate"
and "time spent" fields of any work item. You can also select multiple
iterations in this report if you want a longer view of it.
Regarding the repository metrics, it's not possible with those reports
to do either of the things you ask. The first could be done by modifying
the report template. If you're looking for code delivered into source
control, the namespace is com.ibm.team.scm. This includes things like
change sets, baselines and streams. You can't break this information
down by a particular java project.
james
RTC Reports Team Lead
Hi,
I have some questions about the reports. I am using RTC 2.0.
Is there some doc online on the reports?
Release burndown
We did not use the story points when we did the project. It was a
small project in a class setting.
If we add the story points at this point (now) for each story will we
able to see the release burndown?
Will I then be able to see the team velocity?
Repository metrics
I would like to see the metrics between specific dates. Is that
possible? Is com.ibm.team.repository the namespace for the Java
projects created by users? Can we go into looking a particular Java
projects?
Thanks,
Christelle
The release burndown is designed to work on story points, so if you add
a story points attribute to your work items, and ensure that this
attribute is set as a "top-level work item type" (you can do this in the
project area editor), the release burndown should work. Note that the
release burndown is a view across multiple iterations throughout a
release, with one data point per iteration. Sounds like what you really
want is the regular burndown chart, no? It operations on the "estimate"
and "time spent" fields of any work item. You can also select multiple
iterations in this report if you want a longer view of it.
Regarding the repository metrics, it's not possible with those reports
to do either of the things you ask. The first could be done by modifying
the report template. If you're looking for code delivered into source
control, the namespace is com.ibm.team.scm. This includes things like
change sets, baselines and streams. You can't break this information
down by a particular java project.
james
RTC Reports Team Lead
Hi,
I do not see how to check that the story point attribute is set as a "top-level work item type". Where is it in the project area editor?
I could not use the Project Activity report. I cannot input any parameter - in team area, streams... What is the project activity report and how do es it work?
Thanks,
Christelle
The release burndown is designed to work on story points, so if you add
a story points attribute to your work items, and ensure that this
attribute is set as a "top-level work item type" (you can do this in the
project area editor), the release burndown should work. Note that the
release burndown is a view across multiple iterations throughout a
release, with one data point per iteration. Sounds like what you really
want is the regular burndown chart, no? It operations on the "estimate"
and "time spent" fields of any work item. You can also select multiple
iterations in this report if you want a longer view of it.
Regarding the repository metrics, it's not possible with those reports
to do either of the things you ask. The first could be done by modifying
the report template. If you're looking for code delivered into source
control, the namespace is com.ibm.team.scm. This includes things like
change sets, baselines and streams. You can't break this information
down by a particular java project.
james
RTC Reports Team Lead
I do not see how to check that the story point attribute is set as a "top-level work item type". Where is it in the project area editor?
I could not use the Project Activity report. I cannot input any parameter - in team area, streams... What is the project activity report and how do es it work?
Thanks,
Christelle
On 2/20/2010 4:37 PM, scharffc wrote:
Hi,
I have some questions about the reports. I am using RTC 2.0.
Is there some doc online on the reports?
Release burndown
We did not use the story points when we did the project. It was a
small project in a class setting.
If we add the story points at this point (now) for each story will we
able to see the release burndown?
Will I then be able to see the team velocity?
Repository metrics
I would like to see the metrics between specific dates. Is that
possible? Is com.ibm.team.repository the namespace for the Java
projects created by users? Can we go into looking a particular Java
projects?
Thanks,
Christelle
The release burndown is designed to work on story points, so if you add
a story points attribute to your work items, and ensure that this
attribute is set as a "top-level work item type" (you can do this in the
project area editor), the release burndown should work. Note that the
release burndown is a view across multiple iterations throughout a
release, with one data point per iteration. Sounds like what you really
want is the regular burndown chart, no? It operations on the "estimate"
and "time spent" fields of any work item. You can also select multiple
iterations in this report if you want a longer view of it.
Regarding the repository metrics, it's not possible with those reports
to do either of the things you ask. The first could be done by modifying
the report template. If you're looking for code delivered into source
control, the namespace is com.ibm.team.scm. This includes things like
change sets, baselines and streams. You can't break this information
down by a particular java project.
james
RTC Reports Team Lead
1. Open the project area in the rich client. Click on the Process
Configuration tab. Select Project Configuration > Configuration Data >
Planning > Top-LEvel Work Item Types. Then select your work item type as
a "top-level work item". Then, you need to specify the complexity
attribute... select the "Plan Attributes" item to modify this.
2. The project activity report relates to SCM information - how many
change sets are being added/removed from streams, and how many files and
folders they contain. By default, we don't collect this information in
the data warehouse because it can get very expensive as the number of
streams and sizes of those streams increase. But you can manually tell
the data warehouse which steams to collect data for by going to the Web
UI, clicking on "Reports", then on "Administer SCM Snapshot", then
selecting the streams you want to collect data for. Then, after the
snapshots run again (either manually or automatically overnight) the
report should have parameters and data.
james
RTC Reports Team Lead
On 2/23/2010 1:07 AM, scharffc wrote:
Configuration tab. Select Project Configuration > Configuration Data >
Planning > Top-LEvel Work Item Types. Then select your work item type as
a "top-level work item". Then, you need to specify the complexity
attribute... select the "Plan Attributes" item to modify this.
2. The project activity report relates to SCM information - how many
change sets are being added/removed from streams, and how many files and
folders they contain. By default, we don't collect this information in
the data warehouse because it can get very expensive as the number of
streams and sizes of those streams increase. But you can manually tell
the data warehouse which steams to collect data for by going to the Web
UI, clicking on "Reports", then on "Administer SCM Snapshot", then
selecting the streams you want to collect data for. Then, after the
snapshots run again (either manually or automatically overnight) the
report should have parameters and data.
james
RTC Reports Team Lead
On 2/23/2010 1:07 AM, scharffc wrote:
Hi,
I do not see how to check that the story point attribute is set as a
"top-level work item type". Where is it in the project area
editor?
I could not use the Project Activity report. I cannot input any
parameter - in team area, streams... What is the project activity
report and how do es it work?
Thanks,
Christelle
jmoodywrote:
On 2/20/2010 4:37 PM, scharffc wrote:
Hi,
I have some questions about the reports. I am using RTC 2.0.
Is there some doc online on the reports?
Release burndown
We did not use the story points when we did the project. It was a
small project in a class setting.
If we add the story points at this point (now) for each story will
we
able to see the release burndown?
Will I then be able to see the team velocity?
Repository metrics
I would like to see the metrics between specific dates. Is that
possible? Is com.ibm.team.repository the namespace for the Java
projects created by users? Can we go into looking a particular Java
projects?
Thanks,
Christelle
The release burndown is designed to work on story points, so if you
add
a story points attribute to your work items, and ensure that this
attribute is set as a "top-level work item type" (you can do
this in the
project area editor), the release burndown should work. Note that the
release burndown is a view across multiple iterations throughout a
release, with one data point per iteration. Sounds like what you
really
want is the regular burndown chart, no? It operations on the
"estimate"
and "time spent" fields of any work item. You can also
select multiple
iterations in this report if you want a longer view of it.
Regarding the repository metrics, it's not possible with those reports
to do either of the things you ask. The first could be done by
modifying
the report template. If you're looking for code delivered into source
control, the namespace is com.ibm.team.scm. This includes things like
change sets, baselines and streams. You can't break this information
down by a particular java project.
james
RTC Reports Team Lead