How does Team Concert determine individual progress?

I'm seeing something interesting in the plan editor when grouping by
owner. We work on three week sprints, thus 120h. There are three
days completed in the sprint, thus 24h. So 96h remain in the sprint.
I have people at three different extremes.

User 1:
Planned Work: 162h
Completed Work: 28h
Status: Green

User 2:
Planned Work: 48h
Completed Work: 0h
Status: -10h Red

User 3:
Planned Work: 88h
Completed Work: 12h
Status: -6h Red

Why is it that the person that is the most overloaded is showing up as
green and the other two are showing up red when they have less hours
remaining than the # of hours remaining in the sprint?

Hi Steffan

It's important to understand that load and progress are different. Let
me explain how the progress numbers are computed first. (I assume that
all users work 8h, 5days a week = 40h)

Your three week sprint has 120 working hours and 24 hours are already
completed. The total remaining working time is 80% (96/120=0.8). Now
look at the users. Similar to the ratio above, we compute the ratio of
work left and total work. In a second step we compare the work-ratio and
the realtime-ratio.

User 1:
134/162 = 0.82 ~0.8 -> 0.8 - 0.8 = 0 (On Track)
(Bar will be green as both ratios (realtime/worktime) are equal)

User 2:
48/48 = 1 -> 0.8 - 1 = -0.2 -> (Behind)
Expected Work Done= (48 * 0.2) - 0 = 9.6 ~ 10

User 3:
76/88 = 0.86 ~0.9 -> 0.8 - 0.9 = -0.1 (Behind)
Expected Work Done= (88 * 0.2) - 12 = 5.6 ~ 6

In short, the idea of progress computation is to compare the progress of
real time with the progression of your work (resolving work items). In
case of User 1, read this that he might bit a pessimistic when
estimating. His estimates are high, but so is his fix rate.

In contrast load is the comparison of how much work time do I have and
how much work time do I have allocated. User 1 will be red when the load
is shown.


--
Cheers, Johannes
Agile Planning Team