S
Sean
We are using MS Project 2003 w/MSPS 2003, all the latest patches. We
are having some troubles with one group who uses Project mostly for
time-logging purposes and not for project planning. We have begun
having issues with the accuracy of Actual Work in the Analyzer. For
too many projects the Actual Work in the project does not match the
Actual Work logged in timesheets. These users are not PMs, but just
create projects and accept updates.
We want to provide better training for what users should and should
not do in Project to avoid changing Actual Work. We know some basic
things like "don't touch the Actual Work, % Complete, or Duration
columns", but other than that we don't know what other actions might
alter the actuals in the project. Since the causes we can identify are
limited, we aren't sure what actions may be causing these errors and
if there is any pattern to the user's behavior we need to correct.
What are some other ways that Actual Work can get distorted in a
project?
are having some troubles with one group who uses Project mostly for
time-logging purposes and not for project planning. We have begun
having issues with the accuracy of Actual Work in the Analyzer. For
too many projects the Actual Work in the project does not match the
Actual Work logged in timesheets. These users are not PMs, but just
create projects and accept updates.
We want to provide better training for what users should and should
not do in Project to avoid changing Actual Work. We know some basic
things like "don't touch the Actual Work, % Complete, or Duration
columns", but other than that we don't know what other actions might
alter the actuals in the project. Since the causes we can identify are
limited, we aren't sure what actions may be causing these errors and
if there is any pattern to the user's behavior we need to correct.
What are some other ways that Actual Work can get distorted in a
project?