MSP 2007 - time entry query

[WDP]

After reading all the material available for MS project 2007 I have still 2
questions:

* If a team member is sick, how somebody can introduce his/her ours using
PWA? Who can introduce their hours?

* I have noticed that when using the PWA and updating actual work and
remaining work, in the Project center, task work views, I cannot see
the updated results even they have been approve by the PWA project manager.
I only see them when I connect to MS project 2007 to the
server, and then I got them updated. Is there a reason for that? Is there
any way to get updated results?

Regards,
WDP

 

[Dale Howard [MVP]]

WDP --

To answer your questions:

1. Project Server 2007 allows a member of the Resource Managers group to
create/edit a Surrogate Timesheet on behalf of a resource who is unable to
complete the Timesheet, such as when the resource is out sick. There is no
way for a resource manager to take over the resource's My Tasks page in PWA,
however.

2. It sounds like you are not publishing your project after applying task
updates. After every round of updating a project, the PM must publish the
project changes using File - Publish.

Hope this helps.

 

[WDP]

Hello Dale,
Thanks for the clarifications.
Further I have the following queries wrt MSP 2007:
-------------------
1.-For case 1, if this is the case. How you can avoid people updating
PWA while I am updating hours through MS project professional connected
to the server or not (in order to avoid overwriting).

In other words, when we are replanning or doing things in MS project. Is
there any way to avoid people use PWA, after it has been publish the
first time?
-------------------

Kindly update.

Regards,
WDP

 

[Dale Howard [MVP]]

WDP --

This is purely a people and process issue. Establish a process similar to
the following:

1. Team members enter task updates by Friday afternoon at the end of
business (no exceptions).
2. Project manager receive and approve task updates by Monday at noon (no
exceptions).

Make both of the above a strict training and performance issue, and then
enforce this performance. You simply cannot use Project Server 2007 as a
"free for all." You have to establish standards and processes for using it
effectively. Hope this helps.