Rollup percent complete

[JB]

I am looking at a project plan created by an employee and I am not sure how
to answer this issue. We are using Project Server 2003. However, he is not
using PWA to have the percent work complete updated by his resources.
Instead he is entering them in by hand in the project plan itself. The
problem is that some, not all, of the rollup (summary level) tasks are
showing 99% complete with all of the subordinate level tasks underneath
showing 100% complete. Why is the rollup not showing 100%? Also, he has
resource names attached to the summary level tasks that showing 99%, not 100%
complete. Why is this happening? I noticed that when I delete the summary
level resource, the percent complete changes to 100% like it should. I know
that you are not supposed to have resources for summary level tasks and they
will be changed. However, agian, why is this happening?

 

[Dale Howard [MVP]]

JB --

Your employee screwed up. He/she should not assign resources to summary
tasks, as this is probably the primary source of the problem. Therefore,
he/she should remove resources from all summary tasks. In addition. when a
summary task shows 99% complete, this usually means that there is a
milestone in that summary section that is not marked 100% complete. Hope
this helps.

 

[JB]

Dale,

I agree, they did what I told them not to do when we started this project.
Anyway, I had them remove the names and the percent completes now say 100%.
However, I did not see any tasks marked as milestones in the affected
sections. Why would Project keep a summary level % complete at 99 just b/c
there is a name there? I am confused. Thanks for your help.

 

[James Fraser]

Dale,

I agree, they did what I told them not to do when we started this project.
Anyway, I had them remove the names and the percent completes now say 100%.
However, I did not see any tasks marked as milestones in the affected
sections. Why would Project keep a summary level % complete at 99 just b/c
there is a name there? I am confused. Thanks for your help.

We're in the area of "Undefined Behaviour" so explaining it may not be
perfect, but...
The user assigned to the summary task creates an assignment on that
task. The summary task has work (not its own, but a roll-up of the sub
tasks.) So the assignment may have some work associated with it unless
the resource was assigned at 0% (Can you even do that?). As long as
that work isn't completed, the summary task will not be at 100%.


James Fraser