Schedule Progress

[Tomcat]

I am trying to show schedule progress on a summary bar. For example if I
have 60 hours of work to do over a ten week period, and 30 of these hours are
scheduled to be done in the first four weeks, and I have completed 30 hours I
want my summary progress bar to be 40% of the total summary bar rather than
50%. Consequently if 30 hours were scheduled over the first nine weeks and
the remaining 30 hours were scheduled for week ten, I would want to show the
progress bar as 90% of the total summary bar rather than 50. I thought I
could use a summary progress bar which starts at [start] and ends at [%
complete] to do this, but it doesn't look right. Any help would be
aprreciated

 

[Steve House [Project MVP]]

Progress % Complete in Project always refers to duration, NOT work. I think
what you might be seeing is the effect of the fact that the progress on a
summary task is an imputed weighted average of the subtask progress.
Project sums up the subtask scheduled durations and divides that figure by
the sum of the subtask actual durations. This gives an effective % Complete
for the summary task which is then multiplied by the summary task duration
to compute an effective Actual Duration.

An interesting experiment ... create a summary task with 5 subtasks, linked
FS. Make all the subtasks milestones with zero duration and put 5 days lag
time in each link. The summary task will show 20 days duration. Show the
tracking toolbar and tracking table and mark the first 2 subtasks 100%
complete. The summary will show it started but actual duration and %
complete will remain at zero even though the 2nd task being complete seems
to indicate a week has passed. Mark subtasks 3 and 4 100% complete.
Summary will not show any progress even though we'ved now marked off 3 weeks
worth of milestones as done. Now mark the last task complete - summary
suddenly jumps from 0% to 100% complete and its actual duration jumps from
zero to 20 days.

Without seeing your file it's impossible to say if an identical process is
involved in the results you're seeing but I would expect it to be at least
related to what you'd see in the milestone experiment.