It's all about the answers!

Ask a question

Why does a Story progress bar show "Estimated: 83%" when there is just one estimated task linked to it?


Tim Fuller (471328) | asked Dec 08 '14, 11:13 a.m.
I've created a Story work item and attached a single estimated Task to it.  The Story progress bar shows "Estimated: 83%." I was expecting it to show Estimated: 100%.  Why is it 83%?

2 answers



permanent link
sam detweiler (12.5k6195201) | answered Dec 08 '14, 11:48 a.m.
edited Dec 08 '14, 11:48 a.m.
sometimes there are other child tasks in other iterations..

Comments
Tim Fuller commented Dec 08 '14, 12:18 p.m.

Haven't tried it yet with multiple iterations.  This case is a new project area with just one Story and one Task.  I did discover however that the only way to get the "Estimated: xx%" to read 100% was to have a non-zero story points value on the Story and all the task have the hours estimate.  Having the Story Points field on the Story count toward the Estimated % on the progress bar was not intuitive for me.  Read lots of docs on jazz.net and don't remember that connection. 


permanent link
Tim Fuller (471328) | answered Jan 11 '16, 5:53 p.m.
I took another try at figuring this one out and here's what I've determined for 5.0.1.  The progress bar on the Story work item is what I've started calling a combined progress bar. Combined in that the "Estimated" percentage is actually an average of the Complexity and Time estimates.   So with one Story work item and child Task work items it worked like this:

Case one: Story complexity-unassigned, Task 1-no estimate, Task 2-no estimate --->> Progress Estimated % on Story-50%
Case two: Story complexity-unassigned, Task 1-no estimate, Task 2-estimated --->> Progress Estimated % on Story-67%
Case-three: Story complexity-unassigned, Task 1-estimated, Task 2-estimated --->> Progress Estimated % on Story-83%
Case four: Story complexity-NON-zero value, Task 1-estimated, Task 2-estimated --->> Progress Estimated % on Story-100%

Our initial working assumption was that the Story Progress Estimated percentage would be derived from the child work items.  So in Case one through four the expected %'s would be 0, 50, 100, 100.  The second possibility was that the system was considering the Story as part of the estimate group, so there are actually 3 work items to consider.  So in that case the expected %'s would be 0, 33, 67, 100.  But that's not how it works, either.  What did work was to consider each measure, complexity (Story Points) and Estimate (hours) separately, then average the two. So to get to the results in Case's one through four above it worked this way:

Case One (0 complexity, no task estimated)
Complexity Estimated=100%, tasks estimated 0/3-0%, average 50%

Case Two (0 complexity, one task estimated)
Complexity Estimated=100%, tasks estimated 1/3=33%, average 67%

Case Three (0 complexity, two tasks estimated)
Complexity Estimated=100%, tasks estimated 2/3=67%, average 83%

Case Four (non-zero complexity, two tasks estimated)
Complexity Estimated=100%, tasks estimated 3/3=100%, average 100%

I know this doesn't cover all the options, but I did additional tests with additional children and this calculation scaled up well.

AND you may have noticed the divisor in the fraction for the tasks estimated percentage.  In this example, you might expect it to be 2 since there are two tasks.  To get the numbers to work right you need the total number of work items in the parent/child configuration, so in this case it's 3, 1 story and 2 tasks. Now, why 1 Story without a complexity value shows a Progress Complexity of 100% is still a mystery only IBM can answer.

We checked multiple sources including jazz.net, help files, and even some IBM sources and no one had an answer. 


Comments
Ralph Schoon commented Jan 12 '16, 2:19 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

This is a small introduction: https://jazz.net/library/article/586

Your answer


Register or to post your answer.