I'm trying to figure out the different time spend in each steps of our developement process;
I setup a board with 3 columns + done:
I'm trying to segragated time Upstream, In Progress and Downstream, and while looking at the average values for each of them, I get figures :
Sum = 38 days, 19 hours, 2 minutes
(don't worry about the actual lenght of those, I'm actually more looking at Epics than sprint tasks -:) )
When I select my 3 columns directly, I got average time
In my understanding, those 2 numbers should be exactly the same. I'm obviously using the same time frame and the same filters and swimlanes.
The same behaviour is reflected in the other metrics (standard deviation, running average....)
So my first question is :
Why are they not the same ? Where are those 4 days ?
My second question is about the "Done" column. There is stuff in there, mainly a few tasks that have been "repopened". Can I be certain that those tasks are nevertheless taken into account in the other columns ? Also, are they not introducing the issue above ?
I think I understand your questions here. I believe the difference in numbers is expected behavior. It is a matter of adding up individual averages and considering it same as cumulative average. This will not be the same because of the way cumulative averages are calculated.
Individual averages are calculated like this : (Time elapsed in stage A)/(number of issues that were in stage A)
Total of individual averages will look like : (Time elapsed in stage A)/(number of issues that were in stage A) + (Time elapsed in stage B)/(number of issues that were in stage B) + (Time elapsed in stage C)/(number of issues that were in stage C)
Cumulative averages (which shows up when you select all 3 stages A,B and C on 'Refine' tab) are calculated like this : (Time elapsed in stage A, B and C)/(number of issues that were in stage A, B and C)
As you can see, there is a huge difference in the way these numbers are calculated and hence it is quite normal that they don't total up to be the same, especially if not all issues didn't make it to all stages (A, B and C).
I hope that explanation helps a bit...
Atlassian ranks project attributes as the third most important factor impacting performance in the category of data. It’s not surprising, since project attributes are precisely the rules used to ma...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs