Collecting Actuals using Project Web Access

[Tim Ivey]

I have to use Project Web Access to collect actual hours per tasks.

So here is the senario.
I have a task that is 3 weeks long and I plan on working 4 hours per week

Problem.
If I work 6 hours in the first week and enter this information through PWA, The plan is updated with 4 actual hours in week 1 and 2 actual hours in week too instead of placing all of the hours in week 1.

Do I have a setting wrong. Is this the design of this program.

Any Help, Advice or Guidance is greatly appreciated

 

[Brenda]

You probably do have a setting wrong. It's either at the
task level, on the Advanced tab, do you have it set
to "Task must finish on?" Or under the Schedule tab on
Tools - Options, do you have it turned on "Tasks will
always honor their constraint date?" I've seen this
behavior when these options are set incorrectly for the
way you are managing your project.

-----Original Message-----
I have to use Project Web Access to collect actual hours per tasks.

So here is the senario.
I have a task that is 3 weeks long and I plan on working 4 hours per week

Problem.
If I work 6 hours in the first week and enter this

information through PWA, The plan is updated with 4
actual hours in week 1 and 2 actual hours in week too
instead of placing all of the hours in week 1.

 

[Dale Howard [MVP]]

Tim --

You are not doing anything wrong; the software is performing as designed.
It sounds like you are using the "Actual work done and work remaining"
method of tracking progress in Project Server. When you use this method of
tracking and enter a value in the Actual Work column, Microsoft Project
evenly apportions the Actual Work across the life of the task in accordance
with the original Units assigned to the task. Therefore, since you assigned
a resource at 12 hours of Work across a 15-day Duration task, Microsoft set
the assignment at 10% Units or .8 hours of Work per day. When you enter 6
hours of Actual Work for the task in the Actual Work column in PWA, the
system applies the 6 hours of Actual Work at .8 hours per day for the first
7 days of the task and .4 hours on the 8th day. Thus, it applies 4 hours of
Actual Work during the first week and 2 hours of Actual Work during the
second week.

If this is not the behavior you wish, then I would recommend you use a
different tracking method that would better suit your needs. I believe a
more appropriate choice would be the "Hours of work done per day or per
week" method with the "Users should report their total hours worked for a
week" option. This would allow the resource to enter 6 hours of work for
the first week and have all 6 hours of Actual Work show up during the first
week only. Hope this explanation and recommendation helps.

I have to use Project Web Access to collect actual hours per tasks.

So here is the senario.
I have a task that is 3 weeks long and I plan on working 4 hours per week

Problem.
If I work 6 hours in the first week and enter this information through

PWA, The plan is updated with 4 actual hours in week 1 and 2 actual hours in
week too instead of placing all of the hours in week 1.