Accepting Hours for a Completed Task Causes Actual Hours to Inflate for all Resources

  • Thread starter SecretariatProjects
  • Start date
S

SecretariatProjects

The following scenario is causing major problems for us and I would b
much obliged if someone could assist.

We have a culture in transisiton where about 50% of our resource
remember to submit timesheets on a regular basis. The other 50% fail t
do so and then submit two months worth of hours in one sitting. To wor
around this, Project Managers often go into the plan and zero out th
remaining hours to show that a task is complete.

We need the individual resource timesheets for audit purposes becaus
we capitalize the hours. When those rogue resources finally submi
their back time and the Project Manager accepts their hours, MS Projec
inflates actual hours for ALL resources assigned the tasks bein
updated. As far as I can tell, this only occurs on tasks that ar
showing 100% complete.

An example for clarification:
- John submits 150 hours to the task "Prototype Design" 2 months afte
the task has been marked complete.
- When the PM accepts these hours, MS Project inflates the actual hour
of Suzy, Jim, and Mark by 500 hours (the other resources assigned to th
task "Prototype Design").

This issue is causing us to over-report hours capitalizable and we no
need to back out nearly 3,000 hours from the budget.

Again, we are working on transitioning the culture but any insight o
how to work around this issue in Project would be greatly appreciated
 
G

Gary L. Chefetz

It sounds like you're using Project Server but you don't specify the
version. Try this post again, being certain to specify the version, and post
it to microsoft.public.project.server, rather than here, which is for
client-only questions.
 

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