Progress bar in iteration planning
As trivial as it seems to me, I have trouble finding out how the "Expected work Hours" and subsequently the "Hours behind" are calculated in the Iteration plans...
Any help? Jan |
5 answers
JanVdP wrote:
As trivial as it seems to me, I have trouble finding out how the What we do to calculate the projection is pretty straightforward: We take two ratios and compare them. The first ratio is the sum of work that has been resolved against the sum of work that is still remaining. The second ratio is the sum of real time that's over again the sum of real time that's upcoming. projection= work_time_DONE/work_time_REMAIN - real_time_DONE / real_time_REMAIN You are behind if this value is negative and vice versa. The expected work hours is your total work times the real time progress, e.g. when 20 of 40hrs are over, half of your work is expected to be done (5 of 10pts). The work hours behind/ahead is difference of expected work hours done and actual work time done, e.g. 20 of 40hrs real time are over, but only 1 out of 10 story points have been achieved. As the real time ratio is 0.5 we expect 10*0.5=5 story points to be done. As only 1 point is done, you are behind by 4 points. -- Cheers, Johannes Agile Planning Team |
Johannes thank you for this explanation, we are currently not using story points, they are set to 0 in our tasks. How does that affect expected work hours and ahead/behind number of hours?
Thank you Lila JanVdP wrote: As trivial as it seems to me, I have trouble finding out how the What we do to calculate the projection is pretty straightforward: We take two ratios and compare them. The first ratio is the sum of work that has been resolved against the sum of work that is still remaining. The second ratio is the sum of real time that's over again the sum of real time that's upcoming. projection= work_time_DONE/work_time_REMAIN - real_time_DONE / real_time_REMAIN You are behind if this value is negative and vice versa. The expected work hours is your total work times the real time progress, e.g. when 20 of 40hrs are over, half of your work is expected to be done (5 of 10pts). The work hours behind/ahead is difference of expected work hours done and actual work time done, e.g. 20 of 40hrs real time are over, but only 1 out of 10 story points have been achieved. As the real time ratio is 0.5 we expect 10*0.5=5 story points to be done. As only 1 point is done, you are behind by 4 points. -- Cheers, Johannes Agile Planning Team |
|
lbehzadi wrote:
Johannes thank you for this explanation, we are currently not using That depends on your setting. For team and project release plan we calculate progress based on a complexity attribute. By default, this is story points and, hence, your bars don't make a statement. Iteration plans always use hours for progress computation. The progress computation is actually independent of the unit of work (story points, hours, ...); it works the same for all of them. -- Cheers, Johannes Agile Planning Team |
Just came across this.. The text and the formula don't match. I think the formula should be: work_units_ahead= work_units_DONE - work_units_TOTAL * real_time_PASSED / real_time_TOTAL Or am I just not getting the word 'projection'? /Morten |
The progress is the difference between the Actual Hours and Expected hours.
Actual Hours = (Sum time spent of all the work items)
Expected hours = (Sum estimates of all work items) * (Available hours from Start date of plan till now/ Available hours from Start date to End Date of the plan)
The available hours between 2 dates is calculated based on the allocation, work hours and absences of all the users part of the plan.
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.