Is there a way to customize reports? Story by iteration for
3 answers
On 4/23/2009 11:27 PM, wlobig wrote:
I may be able to help you on this one... in M3 we've done some shuffling
of our Scrum reports and added a couple of new ones:
1. "Story Points by Iteration" became "Team Velocity"
2. The old "Team Velocity" became "Estimated vs Actual Work" (these
changes are more in line with the way the term "Team Velocity" is used.
3. We introduced a new "Story Points by Iteration" report which shows
exactly what you're asking for. The total number of planned/achieved
points, broken down by iteration. You can use this, for example, to
ensure good distribution of story points throughout your release.
The story point-based reports will also honour the new support from APT
to have configurable top-level work items (i.e. they don't have to just
be Stories anymore), and configurable attributes to specify the
complexity (i.e. they don't have to just be "Story Points" anymore).
Hope this helps.
james
Jazz Reports Team Lead
example shows the number of "achieved" points per iteration.
I'd like to know the total number of planned and achieved points per
iteration.
Thanks
I may be able to help you on this one... in M3 we've done some shuffling
of our Scrum reports and added a couple of new ones:
1. "Story Points by Iteration" became "Team Velocity"
2. The old "Team Velocity" became "Estimated vs Actual Work" (these
changes are more in line with the way the term "Team Velocity" is used.
3. We introduced a new "Story Points by Iteration" report which shows
exactly what you're asking for. The total number of planned/achieved
points, broken down by iteration. You can use this, for example, to
ensure good distribution of story points throughout your release.
The story point-based reports will also honour the new support from APT
to have configurable top-level work items (i.e. they don't have to just
be Stories anymore), and configurable attributes to specify the
complexity (i.e. they don't have to just be "Story Points" anymore).
Hope this helps.
james
Jazz Reports Team Lead
On 4/23/2009 11:27 PM, wlobig wrote:
example shows the number of "achieved" points per iteration.
I'd like to know the total number of planned and achieved points per
iteration.
Thanks
I may be able to help you on this one... in M3 we've done some shuffling
of our Scrum reports and added a couple of new ones:
1. "Story Points by Iteration" became "Team Velocity"
2. The old "Team Velocity" became "Estimated vs Actual Work" (these
changes are more in line with the way the term "Team Velocity" is used.
3. We introduced a new "Story Points by Iteration" report which shows
exactly what you're asking for. The total number of planned/achieved
points, broken down by iteration. You can use this, for example, to
ensure good distribution of story points throughout your release.
The story point-based reports will also honour the new support from APT
to have configurable top-level work items (i.e. they don't have to just
be Stories anymore), and configurable attributes to specify the
complexity (i.e. they don't have to just be "Story Points" anymore).
Hope this helps.
james
Jazz Reports Team Lead
Thanks
I assume this means I need to upgrade to the 2.0 beta? I'm a little hesitant to do that at this point in my project, but I wonder if its possible to only upgrade my client and get this functionality? Or do I need the entire server?
Thanks
On 4/24/2009 11:27 AM, wlobig wrote:
Thanks
I assume this means I need to upgrade to the 2.0 beta? I'm a little
hesitant to do that at this point in my project, but I wonder if its
possible to only upgrade my client and get this functionality? Or do
I need the entire server?
Thanks
You'd need the entire server. And the changes I'm mentioning are not in
2.0beta1, but will appear in M3 and subsequent releases.
If you're feeling brave you can modify one of the existing reports - the
report you're asking for is not too much different than the Story Points
by Iteration report in 1.0.1.1. To do this you'd need the BIRT tooling.
james
jmoodywrote:
On 4/23/2009 11:27 PM, wlobig wrote:
example shows the number of "achieved" points per
iteration.
I'd like to know the total number of planned and achieved points
per
iteration.
Thanks
I may be able to help you on this one... in M3 we've done some
shuffling
of our Scrum reports and added a couple of new ones:
1. "Story Points by Iteration" became "Team
Velocity"
2. The old "Team Velocity" became "Estimated vs Actual
Work" (these
changes are more in line with the way the term "Team
Velocity" is used.
3. We introduced a new "Story Points by Iteration" report
which shows
exactly what you're asking for. The total number of planned/achieved
points, broken down by iteration. You can use this, for example, to
ensure good distribution of story points throughout your release.
The story point-based reports will also honour the new support from
APT
to have configurable top-level work items (i.e. they don't have to
just
be Stories anymore), and configurable attributes to specify the
complexity (i.e. they don't have to just be "Story Points"
anymore).
Hope this helps.
james
Jazz Reports Team Lead
Thanks
I assume this means I need to upgrade to the 2.0 beta? I'm a little
hesitant to do that at this point in my project, but I wonder if its
possible to only upgrade my client and get this functionality? Or do
I need the entire server?
Thanks
You'd need the entire server. And the changes I'm mentioning are not in
2.0beta1, but will appear in M3 and subsequent releases.
If you're feeling brave you can modify one of the existing reports - the
report you're asking for is not too much different than the Story Points
by Iteration report in 1.0.1.1. To do this you'd need the BIRT tooling.
james