Release Plan/Release Burndown/Story Points Remaining
Hi
I am a bit confused on the data that is showing up on the above mentioned views. When I hover over my Release Plan, I see Story Points Done: 157 of 567 (410 SP's left). But the Story Points Remaining view shows 296 and also never shows SP above 507 while Release Plan has 567. I would of expected to see 567 and then tending downwards. Can someone explain why this is happening?
Thanks very much!
I am a bit confused on the data that is showing up on the above mentioned views. When I hover over my Release Plan, I see Story Points Done: 157 of 567 (410 SP's left). But the Story Points Remaining view shows 296 and also never shows SP above 507 while Release Plan has 567. I would of expected to see 567 and then tending downwards. Can someone explain why this is happening?
Thanks very much!
2 answers
On 9/1/2009 8:37 PM, arnovick wrote:
I'll let someone from the agile planning team comment on the Release Plan.
The Release Burndown report measures, in story points, the number of
remaining story points at the *beginning* of each iteration. Only
stories which are planned for any of the selected iterations, and owned
by one of the selected teams, are considered. So it's not a continuous
curve - just one sample point per iteration.
In the Story Points Remaining report, you *should* see a daily sample of
the number of "remaining" story points, where remaining is defined as
stories which are not closed. Again, only stories planned for any of the
selected iterations, and owned by one of the selected teams, are considered.
Can you take a close look at the parameters that are selected for the
Story Points Remaining report? (or are you viewing it within the context
of the plan editor)?
Also, I don't think your original assumption is *necessarily* correct.
There may not have been any time when 567 story points were all open
(remaining) at the *same time*. This would only be the case if, say, you
started your release with all stories open and assigned points at the
same time. A more likely scenario is that *some* stories were opened,
and assigned story points, at the beginning of the release (say, no more
than 507 points), and as the release progressed, some stories got closed
(completed), while some new stories got created (or existing stories got
estimated upwards). So it's possible the chart is showing the correct
information.
james
RTC Reports Team Lead
Hi
I am a bit confused on the data that is showing up on the above
mentioned views. When I hover over my Release Plan, I see Story
Points Done: 157 of 567 (410 SP's left). But the Story Points
Remaining view shows 296 and also never shows SP above 507 while
Release Plan has 567. I would of expected to see 567 and then
tending downwards. Can someone explain why this is happening?
Thanks very much!
I'll let someone from the agile planning team comment on the Release Plan.
The Release Burndown report measures, in story points, the number of
remaining story points at the *beginning* of each iteration. Only
stories which are planned for any of the selected iterations, and owned
by one of the selected teams, are considered. So it's not a continuous
curve - just one sample point per iteration.
In the Story Points Remaining report, you *should* see a daily sample of
the number of "remaining" story points, where remaining is defined as
stories which are not closed. Again, only stories planned for any of the
selected iterations, and owned by one of the selected teams, are considered.
Can you take a close look at the parameters that are selected for the
Story Points Remaining report? (or are you viewing it within the context
of the plan editor)?
Also, I don't think your original assumption is *necessarily* correct.
There may not have been any time when 567 story points were all open
(remaining) at the *same time*. This would only be the case if, say, you
started your release with all stories open and assigned points at the
same time. A more likely scenario is that *some* stories were opened,
and assigned story points, at the beginning of the release (say, no more
than 507 points), and as the release progressed, some stories got closed
(completed), while some new stories got created (or existing stories got
estimated upwards). So it's possible the chart is showing the correct
information.
james
RTC Reports Team Lead
On 9/1/2009 8:37 PM, arnovick wrote:
Hi
I am a bit confused on the data that is showing up on the above
mentioned views. When I hover over my Release Plan, I see Story
Points Done: 157 of 567 (410 SP's left). But the Story Points
Remaining view shows 296 and also never shows SP above 507 while
Release Plan has 567. I would of expected to see 567 and then
tending downwards. Can someone explain why this is happening?
Thanks very much!
I'll let someone from the agile planning team comment on the Release Plan.
The Release Burndown report measures, in story points, the number of
remaining story points at the *beginning* of each iteration. Only
stories which are planned for any of the selected iterations, and owned
by one of the selected teams, are considered. So it's not a continuous
curve - just one sample point per iteration.
In the Story Points Remaining report, you *should* see a daily sample of
the number of "remaining" story points, where remaining is defined as
stories which are not closed. Again, only stories planned for any of the
selected iterations, and owned by one of the selected teams, are considered.
Can you take a close look at the parameters that are selected for the
Story Points Remaining report? (or are you viewing it within the context
of the plan editor)?
Also, I don't think your original assumption is *necessarily* correct.
There may not have been any time when 567 story points were all open
(remaining) at the *same time*. This would only be the case if, say, you
started your release with all stories open and assigned points at the
same time. A more likely scenario is that *some* stories were opened,
and assigned story points, at the beginning of the release (say, no more
than 507 points), and as the release progressed, some stories got closed
(completed), while some new stories got created (or existing stories got
estimated upwards). So it's possible the chart is showing the correct
information.
james
RTC Reports Team Lead
Hi James
Thanks very much for you reply. This helps greatly. And yes, this is being viewed from the plan editor. I will let you know if I need further information.
Thanks again James