Points based burndown for the release

On 11/17/2009 6:52 PM, pizza wrote:

Does anyone know if there is a report that exists or can be built that
will show a story points based burndown for the entire release? With a
"product backlog" type plan, I can see progress in completed
story points vs. total story points, and there is a report that shows
me completed / planned story points for each iteration, but I'd like
to see a graphical burndown-like report that shows me an Ideal
burndown and actual burndown across all planned iterations for the
release.

Have you looked at the Release Burndown report? It aims to do exactly
this. There are also a few other Story Points reports (Story Points by
Iteration, Team Velocity) that might help.

james
RTC Reports Team Lead

On 11/17/2009 6:52 PM, pizza wrote:

Does anyone know if there is a report that exists or can be built that
will show a story points based burndown for the entire release? With a
"product backlog" type plan, I can see progress in completed
story points vs. total story points, and there is a report that shows
me completed / planned story points for each iteration, but I'd like
to see a graphical burndown-like report that shows me an Ideal
burndown and actual burndown across all planned iterations for the
release.

Have you looked at the Release Burndown report? It aims to do exactly
this. There are also a few other Story Points reports (Story Points by
Iteration, Team Velocity) that might help.

james
RTC Reports Team Lead

I did look at that report and the title implied it is what I am looking for, but when I run the report and read the description, it is not exactly what I wanted to see. According to the report, it plots the remaining story points as each iteration begins. Well, we have been changing the total points (lowering them) for the entire release, but the points on the chart do not reflect that (yet). It seems like I have to wait until the start of the next iteration to see the big drop. Perhaps this makes sense for what the original design of this report. I will give this one some more thought and see how it goes for a couple of more iterations.

On 11/18/2009 10:52 PM, pizza wrote:

jmoodywrote:
On 11/17/2009 6:52 PM, pizza wrote:
Does anyone know if there is a report that exists or can be built
that
will show a story points based burndown for the entire release? With
a
"product backlog" type plan, I can see progress in
completed
story points vs. total story points, and there is a report that
shows
me completed / planned story points for each iteration, but I'd
like
to see a graphical burndown-like report that shows me an Ideal
burndown and actual burndown across all planned iterations for the
release.


Have you looked at the Release Burndown report? It aims to do exactly

this. There are also a few other Story Points reports (Story Points by

Iteration, Team Velocity) that might help.

james
RTC Reports Team Lead

I did look at that report and the title implied it is what I am
looking for, but when I run the report and read the description, it
is not exactly what I wanted to see. According to the report, it
plots the remaining story points as each iteration begins. Well, we
have been changing the total points (lowering them) for the entire
release, but the points on the chart do not reflect that (yet). It
seems like I have to wait until the start of the next iteration to
see the big drop. Perhaps this makes sense for what the original
design of this report was, but I am looking for a report that is more
like the iteration burndown that keeps up to date with the current
total points and burning down of those points, in addition to an
ideal burn line across the planned iterations. If the number of
iterations or the total points change, then I'd like to see the
report dynamically change.


Can you create an enhancement request describing what you want, and
assign it to the Reports category? We'll take a look during our 3.0
development.

Thanks,

james

We are in the first days of an iteration. When I run a query for the completed stories in the current iteration, I have total of 3 story points. When I run team velocity report, it shows the bar at 4 points. Why the difference?
thanks,

I am also confused about the release burn down report. We have 3 iterations in the release, we are currently in iteration 2. I expected the release burn down report would show me the total planned points for the entire release (aka 3 iterations) and show the current burn down ( as of iteration2) compared to the total.
Whereas all I see on the report is iteration 1 and iteration 2, nothing about iteration 3, total planned includes story points for iteration1 and 2.

So my question then: what does "release" mean in this report then?

thank you
Aysim

The Burndown and Burnup reports are really nice with trendlines etc. The Burndown/Burnup reports use the ideal hours of the tasks.
We'd like to use similar charts for our release burndown chart.

I know the Story Points Remaining report as well as the Release Burndown report, both using story points. But these reports do not have trendlines to indicate whether we'll hit our target date.
How to we get to a burndown chart that has the features of the Burndown/Burnup reports but works on story points instead of hours?

Thank you,
Juergen

On 3/15/2010 9:08 AM, baumannj wrote:

The Burndown and Burnup reports are really nice with trendlines etc.
The Burndown/Burnup reports use the ideal hours of the tasks.
We'd like to use similar charts for our release burndown chart.

I know the Story Points Remaining report as well as the Release
Burndown report, both using story points. But these reports do not
have trendlines to indicate whether we'll hit our target date.
How to we get to a burndown chart that has the features of the
Burndown/Burnup reports but works on story points instead of hours?

Thank you,
Juergen

We don't currently have such a report. You may want to follow this work
item, which requests a number of enhancements to the release burndown
report that we are considering:

https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/95675

james
RTC Reports Team Lead

Our team is new to RTC, I am looking at the brundown chart for all the teams for the entire release. But, the burndown chart shows that our release ends much sooner than we expect. Since we have only entered story points (no time estimate) for the backlog items, I am wondering if our story points are correct. How many story points do you enter to show one staff month?

Thanks in advance.

Here is a really good explanation of story points...http://en.wikipedia.org/wiki/Story_points

It really does take some getting used to.