Timesheet and Task update process

[ghostme]

Hello guys,
I am currently undertaken a test deployment of Project server 2007 for a
client, during the business requirements gathering i found out that the users
will be practically filling in the same time they fill in the task update
page and in the My timesheet features.
The task updates is to update and track the project schedule while the
timesheets are used to report time spent on the project tasks.

What is the best way for me to configure both the task and timesheet
settings. Should i enforce the synchronization of timesheet hours with hours
reported on task update? or otherwise.

Thank you

 

[Jonathan Sofer]

If you need to keep the time in the timesheets and the projects aligned you
have two options.

- Drive "project tasks" from "my tasks" and then populate "my timesheets"
(actuals will come in automatically on timesheet creation), add other non
project timesheet hours and submit timesheet.
- Drive "project tasks" from "my timesheet" (use import timesheets to
populate actuals in my tasks)

At present I see three issues:
1) In both cases there is a point where the information becomes
unsynchronized
2) In both cases there is a requirement for a two step update process by the
user
3) In both cases a lot of manual steps are required.

If you want to keep the two as synchronized as possible, you will probably
want to turn on the setting that forces My Tasks to be updates by the Import
Timesheet feature only. The problem with this is that it does not allow
your resources to update any other information in My Tasks (it makes the
screen read only). So if you have a requirement to have resources report
"Remaining Work" for example, this will not be a viable solution. Also, the
import timesheet is very hard to use when you start having many timesheets
periods to pick from, there is no order to the timesheets listed in the
Import Timesheet screen.

You might consider trying out the Codeplex Tied-Mode solution which imports
your timesheet hours automatically into My Tasks and submits it to the PM
for approval. This makes "My Timesheets" the single data entry point for
updates. But again, users will have to update remaining work separately and
re-submit the updates. Can get ugly.

http://www.codeplex.com/AutoStatusService

There is talk of this tied-mode solution being incorporated into Service
Pack 2 but that is not final yet.

 

[ghostme]

Jonathan many big thanks for the professional insight once again.
Well i think what i would just suggest is the drive "project tasks" from "my
task" and then populate "my timesheet" automatically.

I have observed the import timesheet to populate "my tasks" to be a little
bit cumbersome when it comes to reporting future timesheet period.

I observed that if the task doesn't fall in the timesheets' period dates
when you try to import the timesheet into the "my task" page no preview shows
up

I will have to observe the first option with some pilot users. Thank you so
much for the insight.

Cheers