Actual Work is changing

[Jill B.]

I have a situation that when changing the duration of a
task after actual work has been reported on that task is
changing the entry of actual work. The user is confused
and believes that once you enter actual work, it should
never change because it's actual. This appears to only
be happening when the duration is decreased, not
increased.

Could someone explain why actual work is changing at
all?

 

[Kevin Flanagan]

It is going to depend on the task type. Wheteher it is
fixed work, fixed duration or fixed units and whether or
not it is effort driven will provide varied results
depending on what is changed. Actual work is just a
record of reality and things will change. That's why
there are 10 baselines to utilize so you can have a
record of what is happening over time.

 

[Gary Chefetz [MVP]]

Jill:

I like to refer to work, duration and units as Project's "holy trinity."
You can set two - Project always calculates the third. Further, Project is
biased to not change units whenever possible. Therefore, with a task set as
fixed-duration which tells Project that it can't recalculate duration, and
because resources are already assigned, the expected behavior is that the
system will adjust work. You need to teach Project fundamental behaviors to
your client.

--
Gary Chefetz [MVP]
http://www.msprojectexperts.com
"We wrote the book on Project Server"

*** Remember to look for line breaks in links posted to the news group, use
cut and paste for these.