Gantt Chart (Project Center) View

[Darrell]

What drives the Gantt Chart view seen in the Project Center?

I ask because progress on some schedules is never accurate and I have combed
through those schedules trying to find a cause without success. My test
schedules seem to update progress correctly and immediately. Other schedules
managed by many different project managers never seem to display the correct
progress and never update even when all work prior to the status date shows
complete with no remaining work.

Can milestones cause an issue with this view?

Stumped again
Darrell

 

[Dale Howard [MVP]]

Darrell --

The information you see in the Project Center page is derived from the
Project Summary Task (Row 0 or Task 0) data in the actual Microsoft Project
2007 plan. If the data between the enterprise project and the Project
Center is "out of synch", the cause is usually the PM forgetting to publish
the enterprise project after the latest updates to the plan. Hope this
helps.

 

[Darrell]

Dale,

You are correct about the schedules not being published and getting that
done took care of several of the schedules not showing the correct amount of
progress. However, I have several schedules that appear to be correctly
statused and have been published that do not show the correct amount of
progress.

In fact, I saved one of these schedules to my desktop and then saved it
again to a development environment. It now shows the correct amount of
progress in the Project Center view and I made no changes to the schedule,
which really makes me wonder what was repaired/corrected/changed when I saved
the schedule (twice) too make it suddenly display accurately. I did notice a
30 day difference in duration but assumed it was a difference in enterprise
calendars.

One other commonality with these schedules is that they were all migrated
from a 2003 server.


Any ideas?

Darrell

 

[Dale Howard [MVP]]

Darrell --

I'm glad we were able to solve part of the problem. Most people who used
Project Server 2003 previously were probably not aware that when they closed
an enterprise project, the system automatically PUBLISHED their project
without their permission or knowledge using a Collaborate - Publish -
Project Plan publishing operation. This functionality was removed in
Project Server 2007, which means each PM must intentionally publish each
project after making any changes to it. So, that definitely makes this a
training and performance issue.

On the other hand, f you have any projects that don't seem to publish, which
is what I suspect is going on with the remaining projects, then I strongly
suspect that they may have gotten corrupted somewhere along the line (either
in 2003 or in 2007). Failing to publish is usually a sign of corruption.
The way to solve this is to save the project as an XML file, delete the
project from the Project Server database, and then import it back into
Project Server using the Import Project Wizard. Hope this helps.