N
Nuala
I know there is a problem with this for which we are awaiting a hot
fix, post service pack 1 but can any one suggest a work around?
The specific problem I have:
We are using timesheeting and our project team are submitting their
acutal time weekly.
With one specific task, we have remaining work of 160days and two
resources assigned. We are using the fixed duration effort driven
combination for allocation of work. I have used as finish no earlier
constraint for the end date for this task. I have adjusted the work
profile to flat, so before synching with actuals, the planned work
looks fine with one days work for each resource until the end date,
which is as you would expect, but as soon as I save the plan and sync
with actuals, the work allocation changes and each resource has all
the work to perform in one day!
This of course throws our utilisation & work forecast cost per month
completely off.
Please can anyone advise if I am approaching this correctly or advise
an alternative approach
Thanks
fix, post service pack 1 but can any one suggest a work around?
The specific problem I have:
We are using timesheeting and our project team are submitting their
acutal time weekly.
With one specific task, we have remaining work of 160days and two
resources assigned. We are using the fixed duration effort driven
combination for allocation of work. I have used as finish no earlier
constraint for the end date for this task. I have adjusted the work
profile to flat, so before synching with actuals, the planned work
looks fine with one days work for each resource until the end date,
which is as you would expect, but as soon as I save the plan and sync
with actuals, the work allocation changes and each resource has all
the work to perform in one day!
This of course throws our utilisation & work forecast cost per month
completely off.
Please can anyone advise if I am approaching this correctly or advise
an alternative approach
Thanks