It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,882

question asked: Jan 14 '09, 11:14 a.m.
question was seen: 5,028 times
last updated: Jan 14 '09, 11:14 a.m.

Related questions

Should sprint's progress bar equal sum of team members'?

0
Paul Sims (315●1●34●21) | asked Jan 14 '09, 11:14 a.m.
One of our ScrumMasters dropped by this morning to show me his sprint backlog in the RTC client.

He observed that the sum of the individual team member contributions doesn't agree with the sprint progress bar. The time spent (294 hours) and estimated time (808 hours) agree, but the time ahead/behind is different. The sum of the individual contributions is 24 hours (behind). The sprint progress bar indicates 40 hours (behind).

Is there a logical explanation for the discrepancy, or is this a bug? (We clicked refresh to force recalculation and the discrepancy remained.)

Paul Sims
IBM WebSphere Commerce

One answer

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Dirk Baeumer (481●1) | answered Jan 20 '09, 6:28 a.m.
JAZZ DEVELOPER
Hi Paul,

this is a bug and the number should be the same. Can you please open a
bug report against agile planning.

Thanks

Dirk Bumer
Agile Planning Component

sims wrote:
One of our ScrumMasters dropped by this morning to show me his sprint
backlog in the RTC client.

He observed that the sum of the individual team member contributions
doesn't agree with the sprint progress bar. The time spent (294
hours) and estimated time (808 hours) agree, but the time
ahead/behind is different. The sum of the individual contributions
is 24 hours (behind). The sprint progress bar indicates 40 hours
(behind).

Is there a logical explanation for the discrepancy, or is this a bug?
(We clicked refresh to force recalculation and the discrepancy
remained.)

Paul Sims
IBM WebSphere Commerce

Your answer

Register or 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.