Plans, workitems, snapshots and reports
Hi,
I think I've got most of the intertwining of the subject objects nearly within my conceptual grasp. I do have one question, however, as one Project Area user has determined that the burn-down for one sprint should show a graph of current vs completed work items. For example, a viewlet using the Burndown report for the project area shows no graph and the message
"No open work items with estimates specified were found."
I have found that the plan contained exactly 1 Story in the resolved or done state. It had 0 pt for Story Points. Changing to 1pt had no effect on the burndown report
One thing about the plan and its work items I have noticed:
Plan dates Aug 18, 2009 - Nov 30, 2009
Work Items 12 have creation dates between Oct 1 and Nov 30, 2009
48 between Dec 1 and Dec 31 2009 and more ..
My question is: Do the creation dates play into the computation of the burndown ? How about the activities on the work items outside the barriers of the sprint boundaries ?
Thanks,
Kevin
I think I've got most of the intertwining of the subject objects nearly within my conceptual grasp. I do have one question, however, as one Project Area user has determined that the burn-down for one sprint should show a graph of current vs completed work items. For example, a viewlet using the Burndown report for the project area shows no graph and the message
"No open work items with estimates specified were found."
I have found that the plan contained exactly 1 Story in the resolved or done state. It had 0 pt for Story Points. Changing to 1pt had no effect on the burndown report
One thing about the plan and its work items I have noticed:
Plan dates Aug 18, 2009 - Nov 30, 2009
Work Items 12 have creation dates between Oct 1 and Nov 30, 2009
48 between Dec 1 and Dec 31 2009 and more ..
My question is: Do the creation dates play into the computation of the burndown ? How about the activities on the work items outside the barriers of the sprint boundaries ?
Thanks,
Kevin
4 answers
Kevin,
some information on how all that works can be found here http://jazz.net/projects/rational-team-concert/learnmore/.
For the Burndown/Burnup charts it is relevant to consider which attributes need to be set. At least The story points, the filed against and the planned for contribute to the report. If the story was closed with planned for set to another iteration it won't contribute. Also if filed against is not in the scope of your report you'd see nothing and get the message below.
Ralph
some information on how all that works can be found here http://jazz.net/projects/rational-team-concert/learnmore/.
For the Burndown/Burnup charts it is relevant to consider which attributes need to be set. At least The story points, the filed against and the planned for contribute to the report. If the story was closed with planned for set to another iteration it won't contribute. Also if filed against is not in the scope of your report you'd see nothing and get the message below.
Ralph
Hi,
I think I've got most of the intertwining of the subject objects nearly within my conceptual grasp. I do have one question, however, as one Project Area user has determined that the burn-down for one sprint should show a graph of current vs completed work items. For example, a viewlet using the Burndown report for the project area shows no graph and the message
"No open work items with estimates specified were found."
I have found that the plan contained exactly 1 Story in the resolved or done state. It had 0 pt for Story Points. Changing to 1pt had no effect on the burndown report
One thing about the plan and its work items I have noticed:
Plan dates Aug 18, 2009 - Nov 30, 2009
Work Items 12 have creation dates between Oct 1 and Nov 30, 2009
48 between Dec 1 and Dec 31 2009 and more ..
My question is: Do the creation dates play into the computation of the burndown ? How about the activities on the work items outside the barriers of the sprint boundaries ?
Thanks,
Kevin
Ralph,
What about resolution dates outside the sprint boundaries ? Exactly 0 of the work items associated with the sprint have closure (Resolution) dates before the end of the sprint.
What about resolution dates outside the sprint boundaries ? Exactly 0 of the work items associated with the sprint have closure (Resolution) dates before the end of the sprint.
Kevin,
some information on how all that works can be found here http://jazz.net/projects/rational-team-concert/learnmore/.
For the Burndown/Burnup charts it is relevant to consider which attributes need to be set. At least The story points, the filed against and the planned for contribute to the report. If the story was closed with planned for set to another iteration it won't contribute. Also if filed against is not in the scope of your report you'd see nothing and get the message below.
Ralph
Hi,
I think I've got most of the intertwining of the subject objects nearly within my conceptual grasp. I do have one question, however, as one Project Area user has determined that the burn-down for one sprint should show a graph of current vs completed work items. For example, a viewlet using the Burndown report for the project area shows no graph and the message
"No open work items with estimates specified were found."
I have found that the plan contained exactly 1 Story in the resolved or done state. It had 0 pt for Story Points. Changing to 1pt had no effect on the burndown report
One thing about the plan and its work items I have noticed:
Plan dates Aug 18, 2009 - Nov 30, 2009
Work Items 12 have creation dates between Oct 1 and Nov 30, 2009
48 between Dec 1 and Dec 31 2009 and more ..
My question is: Do the creation dates play into the computation of the burndown ? How about the activities on the work items outside the barriers of the sprint boundaries ?
Thanks,
Kevin
Kevin,
to be honest, I am not sure. I'd have to try it too. If you look at the graphs you get dots spread over the iteration, so I would assume that the date plays a role.
Ralph
to be honest, I am not sure. I'd have to try it too. If you look at the graphs you get dots spread over the iteration, so I would assume that the date plays a role.
Ralph
Ralph,
What about resolution dates outside the sprint boundaries ? Exactly 0 of the work items associated with the sprint have closure (Resolution) dates before the end of the sprint.
On 5/4/2010 10:08 AM, rschoon wrote:
We're following up in a work item, but the short answer is the
following: The burndown report scopes itself to within iteration
boundaries (whichever iteration(s) are selected). However, even if a
resolution date is outside this range, the work item will still be
considered in the burndown count (i.e. it will contribute to the sum of
hours). So something else is going on, or there is a bug.
james
RTC Reports Team Lead
Kevin,
to be honest, I am not sure. I'd have to try it too. If you look at
the graphs you get dots spread over the iteration, so I would assume
that the date plays a role.
Ralph
yzwkzfnwrote:
Ralph,
What about resolution dates outside the sprint boundaries ? Exactly
0 of the work items associated with the sprint have closure
(Resolution) dates before the end of the sprint.
We're following up in a work item, but the short answer is the
following: The burndown report scopes itself to within iteration
boundaries (whichever iteration(s) are selected). However, even if a
resolution date is outside this range, the work item will still be
considered in the burndown count (i.e. it will contribute to the sum of
hours). So something else is going on, or there is a bug.
james
RTC Reports Team Lead