Best Practices for timesheet info driving schedules

A

Amy Booth Denver

Any ideas where I can get some best practices examples when using % complete
as the tracking method in PWA? or when using Actual and Remaining work as the
tracking method? Especially as all relates to task type.

MSPS 2003
 
M

Marc Soester

Hi Amy,

The main issue you will have with % complete is that your staff cannot
update "remaining work" since this will change the % complete again.

I dont know of a "best practise" but our experience has shown that actual
hours and remaining hours are a very good way of tracking your progress and
actual time of a project. It seems to be the most accurate time.

I am sure that you know that you have 3 tracking methods within Project Server
1. % complete
2. Actual time per day
3. actual time per task

with option 2 and 3 you have the abillity to amend your remaining work and
as a PM it will allow you how your true progress of a project is.

My suggestion would be, if possible use option 2 or 3. ( Somethimes option 1
may be a good one, especially for very long projects, where you dont track
actual time, but as mentioned earlier, it will not allow you to track
remaining work.)

Should you want to use option 2 or 3 I would implement a process whereby
your staff has to enter the inforamtion on a predifined day ( daily, once a
week, once a month etc). Additionally I would also make sure that your PM's
update the Status date of the project after accepting time from your Team
members. This status date can be displayed via PWA, allowing you or the
deparment head to check if all projects are up to date.

I hope this will help you a little and please let me know if you need any
further assistance.
Thanks
Marc
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top