M
microsoft
We're using PWA 2003. I'm hoping someone might be able to answer a
question related to a posting that was made in July of this year. I'm
looking at implementing the Actual Start/Finish tracking in Project
Web Access. However, when I select the Actual Finish column (as an
assignment) to publish (and allow the user to change) I get an alert
explaining that this is not recommended as data loss can occur for
tasks with multiple resources. I'm hoping you can provide a little
insight into this, what effect it will have, and whether it's OK to
proceed. Many of these tasks have multiple resources.
Thanks,
Here's the previous post
=====>>
Mike -- The answer to both of your questions depends on your method of
tracking. It sounds from your message like you are using the % Work
Complete method of tracking. If this is the case, then it is difficult
to show an early finish date for a task without using the Actual Start
and Actual Finish fields in each team member's timesheet. And using
these fields will require some training of your people to use them
correctly. The methodology for using these fields properly would be to
ask your team members to submit progress as follows: 1. When you
actually begin work on a task, enter the date in the Actual Start
field 2. Each week, set the estimated % Work Complete for the task 3.
When the task actually finishes, DO NOT enter 100% in the % Work
Complete field, but instead, enter the date in the Actual Finish field
4. If a task finishes early, then do an immediate update to the
project manager (preferably followed by a phone call as well) The
project manager should immediately approve the task update and then
republish using Collaborate - Publish - All Information. The PM should
probably call the resource on the next dependent task to notify them
of an early start on their task.
question related to a posting that was made in July of this year. I'm
looking at implementing the Actual Start/Finish tracking in Project
Web Access. However, when I select the Actual Finish column (as an
assignment) to publish (and allow the user to change) I get an alert
explaining that this is not recommended as data loss can occur for
tasks with multiple resources. I'm hoping you can provide a little
insight into this, what effect it will have, and whether it's OK to
proceed. Many of these tasks have multiple resources.
Thanks,
Here's the previous post
=====>>
Mike -- The answer to both of your questions depends on your method of
tracking. It sounds from your message like you are using the % Work
Complete method of tracking. If this is the case, then it is difficult
to show an early finish date for a task without using the Actual Start
and Actual Finish fields in each team member's timesheet. And using
these fields will require some training of your people to use them
correctly. The methodology for using these fields properly would be to
ask your team members to submit progress as follows: 1. When you
actually begin work on a task, enter the date in the Actual Start
field 2. Each week, set the estimated % Work Complete for the task 3.
When the task actually finishes, DO NOT enter 100% in the % Work
Complete field, but instead, enter the date in the Actual Finish field
4. If a task finishes early, then do an immediate update to the
project manager (preferably followed by a phone call as well) The
project manager should immediately approve the task update and then
republish using Collaborate - Publish - All Information. The PM should
probably call the resource on the next dependent task to notify them
of an early start on their task.