Is the RTC behavior for task totals as expected?
I found out a situation that I can not explain the reason.
One story has 3 tasks:
task 1 -- estimate 4 hours, status in progress, time remaining 3 hours
task 2 -- estimate 3 hours, status not started
task 3 -- estimate 2 hours ,status not started
My task total shows 1 hour time spent, 9 hours total. (1/9)
Case 1: I change task 1 status to "drop", my task total changes to 6
Case 2: (independent of case 1). I change task 2 status to drop, my time spent changes to 4, task total stays at 9 hours
In summary, dropping an in progress task removes the remaining hours from the task total ( which is fine)
But dropping a not started task adds up to the time spent, which should not be the case.
Is this an issue in the tool?
thank you
Aysim Dalmau
One story has 3 tasks:
task 1 -- estimate 4 hours, status in progress, time remaining 3 hours
task 2 -- estimate 3 hours, status not started
task 3 -- estimate 2 hours ,status not started
My task total shows 1 hour time spent, 9 hours total. (1/9)
Case 1: I change task 1 status to "drop", my task total changes to 6
Case 2: (independent of case 1). I change task 2 status to drop, my time spent changes to 4, task total stays at 9 hours
In summary, dropping an in progress task removes the remaining hours from the task total ( which is fine)
But dropping a not started task adds up to the time spent, which should not be the case.
Is this an issue in the tool?
thank you
Aysim Dalmau
6 answers
On 2/18/2010 12:38 PM, adalmau wrote:
Are you using the Team Velocity report? Or some other means of
calculating the velocity? If you're using the report, the height of each
bar represents the sum total of all story points represented by *closed*
story work items targeted for that iteration.
james
RTC Reports Team Lead
Hi,
I ran a query to verify the reported velocity and realized that
dropped stories (with story points) are also included in the velocity
calculation for the iteration.
Shouldn't velocity be only "completed" story points?
thank you,
Aysim Dalmau
Are you using the Team Velocity report? Or some other means of
calculating the velocity? If you're using the report, the height of each
bar represents the sum total of all story points represented by *closed*
story work items targeted for that iteration.
james
RTC Reports Team Lead
On 2/18/2010 12:38 PM, adalmau wrote:
Hi,
I ran a query to verify the reported velocity and realized that
dropped stories (with story points) are also included in the velocity
calculation for the iteration.
Shouldn't velocity be only "completed" story points?
thank you,
Aysim Dalmau
Are you using the Team Velocity report? Or some other means of
calculating the velocity? If you're using the report, the height of each
bar represents the sum total of all story points represented by *closed*
story work items targeted for that iteration.
james
RTC Reports Team Lead
Hi james,
What do you literally mean when you refer to *closed* items, complete and dropped?
I run the team velocity report and micro team velocity report for our past iteration. It shows on the Y axis 127.5 points. when I run a query for the past iteration for complete stories, I get 124.5 points. The difference of 3 points belong to a story that was dropped. There was no task that was marked complete under that dropped story.
Thank you
Aysim
I want to custom a report, and I need the total "time spent", the total "estimate", but some work item lots of subitem which also contain some children, so I find it is difficult to calculate the the total result using BIRT, because using the Jazz Data Source, I can not operate the data with SQL.
There is any good method to calculate those total values? Thanks.
There is any good method to calculate those total values? Thanks.