Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

How does RTC derive the "Expected Story Points" in the Progress bar in a plan view?

 In 6.0.2 we have several agile teams sharing a PA with each team having their own individual team area. Team A has 120 points planned for the current sprint. The progress report when hovering over their Sprint Backlog plan progress bar says "Expected story points" is 70 points and that they are behind by 27.72 points. They have completed 42\120 points.


Team B is using the same exact Ranked List view and same Sprint Backlog plan type. They have 68 points planned for this sprint but the hover says they have 0 expected story points. Because of having no expected points in the progress bar, their progress is green when it should really be mostly red as they have only completed 6 points so far.

The differences between the teams that I can see is that Team A has estimated 100% of their items and they use estimated Features as parent items to the stories, the Features are ranked. Team B has estimated 88% of their sprint backlog and are not using Features as parents, they are ranking their stories. 

The Question is how is RTC coming up with the "expected" story points for the sprint? Is it based on the rate that stories are getting closed? 

I know that the calculation is: RealTimeProgress =

    RealTimeDone[resolved] / (RealTimeDone[unresolved] + RealTimeLeft) 

    But this doesn't clearly explain why one team would show as having an "Expected" number of points and another team has none, when both teams have planned points and are progressing through the same sprint? Have searched this forum, IBM Support and IBM Tech Notes without finding an explanation. Very grateful for any insights into this mechanism....

0 votes



One answer

Permanent link

 https://jazz.net/help-dev/clm/index.jsp?re=1&topic=/com.ibm.team.apt.doc/topics/c_review_progress_web.html&scope=null  


This section in IBM Rational Help addresses the details of how the progress bars track work, knowing past rates of completion. This makes it clear it is essential to use estimates of hours as well as your points to get valuable information from the progress bars.

0 votes

Your answer

Register or log in to post 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.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details
× 12,014
× 1,381
× 1,220

Question asked: Jul 18 '18, 3:51 p.m.

Question was seen: 3,538 times

Last updated: Aug 03 '18, 5:52 p.m.

Confirmation Cancel Confirm