September 28 & 29, 2020 | Virtual
Please login or join to subscribe to this thread
Hi Lea, Is it something that you can program manually. I believe should be a constraint that you introduce to planned MHRS which keeps them the same all the way for comparison purposes. That's what crossed my mind ....
Hi Lea, can you tell me what view your use to update your actuals? Usually, when you enter the actuals, the remaining hours should change to the difference between the estimated and the actuals. Is it possible that you enter the actuals after the projected Finish Date? If so, it could be that Project Server, assumes the task is over and, thus, completed.
I agree with Rami and Stephane and I also would suggest to baseline your plan before you can start entering actual progress. Moreover if there is a change in plan resultantly, plan must be re-baselined and everything will turn out right.
Thank you for the suggestion. I'm going to try it and see if it works.
I use the Resource Usage view and click on Ctrl F - (enter Resource Name) to view and enter Actual Work. I'm not entering the actuals after the projected finish date. But that's a good question. Yes, the remaining hours are changing to the difference between the estimated and the actuals.
Please allow me to elaborate on my initial question:
If I estimate that Resource A is going to work 166 in a month for Dev testing but actually Resource A works 150 hours. When I enter 150 in Project Server, Estimated Work hours change to 150. I want Estimated Work hours to remain 166 so that at the end of the year, when I have to provide an Actuals for the year and projections for the next year I can refer back to the original # of Estimated Hours.
Please let me know if any additional information is needed.
The entire project has been baselined. In theory I am in full agreement that if you re-baseline the plan everything will work out however in this case, because the baseline has been set at the EPMO level - I can't re-baseline the project as it will affect all other projects.
I take it you enter the actuals in the grid section of the view? If so, make sure that you enter the time against Actual Work.
By default the Resource Usage view only shows and accepts Work values - which are, of course, your estimates.
Right-click on the grid and select Actual Work. That's the grid cell you want to enter the values in.
The discussion has migrated into two threads - one regarding Project Server and one regarding EPMO. Here is my feedback.
While I do not use Project Server, more data needs to be reviewed in conjunction with recording actual hours used by Richard in a month. The data might emerge by asking questions on Richard's activity, such as What is the status of the activity. How many hours are required to complete the activity. Why is there a variance on the actuals manhours vs scheduled manhours.
EPMO is maintaining a Program Master Schedule, which includes resource management to assure project assignments and availability of manpower are aligned. As needed, the EPMO may shift resources to maximize utilization, thereby reducing any overhead expenses from resources without assigned work. If Richard did not complete his activity, his resource assignment will be adjusted to the next month so the activity can be completed. Of course, this may means that a new activity by Richard on this project or another project may be delayed.
Please login or join to reply