C
Clark
This falls into the category of "wanting to have my cake and eat it too." In
our organization, we need to plan with estimated WORK for each individual
task. This then aggregates to the total hours and time phasing for the
various resources using either the TASK USAGE or RESOURCE USAGE views. This
can be baselined for tracking against ACTUAL WORK in the future.
My issue arises when we get into project execution. One "right" way to use
Project is to collect ACTUAL WORK data on each task as it is conducted and
enter that into the time phased matrix on TASK USAGE or RESOURCE USAGE. (We
do NOT use Project Server.) Unfortunately, in our orgnization, there is no
support to collect information at this level of granularity. We get hour
reporting for the project, but not individual tasks. We CAN get people to
provide information about task status, but not actual hours against that
task. (AND we need to be able to track resource hours against plans for
purpose of forecasting. Hour reporting is taking place in a stand-alone
system.)
The current compromise approach I am using is to collect all planned and
actual hours under ONE task. Once the project is planned and baselined, I
manually enter planned hours (WORK) in the time phased matrix for each
resource assigned, using a single task and the TASK USAGE view. I then
"manually" zero out the "WORK" on all other tasks/resources in the project
plan. This will LEAVE the baseline work on the individual tasks/resources,
but the only place where planned effort (WORK) remains is on my tracking
task. When hours are reported on a weekly basis, I enter ACTUAL WORK in the
time phased matrix for each individual resource on the tracking task. When
these entries don't match the planned hours, remaining hours will be shifted
- which is fine. I will also use the % complete column to track status on
the other (NOT tracking) tasks and adjust durations, start-no-earlier-than,
etc. as necessary to monitor progress.
So far so "good..." albeit not "pure." The above approach lets me see
progress on tasks as well as track planned versus actual hours. The PROBLEM
arises when/if I need to carry out major replanning. Except for the tracking
task, I no longer have planned (WORK) hours on the "real" project tasks (I
only have BASELINE WORK for those tasks) that shifts with changes in
start/finish dates, etc. For major replanning, I end up needing to move
hours BACK to the individual tasks (under WORK), make my adjustments, and
then go back through the approach discribed above. NOT something that most
people would use (some would say, waste) their time doing.
I am interested in any comments from others who may have this same issue and
how you have addressed it.
Sorry for the long post!
our organization, we need to plan with estimated WORK for each individual
task. This then aggregates to the total hours and time phasing for the
various resources using either the TASK USAGE or RESOURCE USAGE views. This
can be baselined for tracking against ACTUAL WORK in the future.
My issue arises when we get into project execution. One "right" way to use
Project is to collect ACTUAL WORK data on each task as it is conducted and
enter that into the time phased matrix on TASK USAGE or RESOURCE USAGE. (We
do NOT use Project Server.) Unfortunately, in our orgnization, there is no
support to collect information at this level of granularity. We get hour
reporting for the project, but not individual tasks. We CAN get people to
provide information about task status, but not actual hours against that
task. (AND we need to be able to track resource hours against plans for
purpose of forecasting. Hour reporting is taking place in a stand-alone
system.)
The current compromise approach I am using is to collect all planned and
actual hours under ONE task. Once the project is planned and baselined, I
manually enter planned hours (WORK) in the time phased matrix for each
resource assigned, using a single task and the TASK USAGE view. I then
"manually" zero out the "WORK" on all other tasks/resources in the project
plan. This will LEAVE the baseline work on the individual tasks/resources,
but the only place where planned effort (WORK) remains is on my tracking
task. When hours are reported on a weekly basis, I enter ACTUAL WORK in the
time phased matrix for each individual resource on the tracking task. When
these entries don't match the planned hours, remaining hours will be shifted
- which is fine. I will also use the % complete column to track status on
the other (NOT tracking) tasks and adjust durations, start-no-earlier-than,
etc. as necessary to monitor progress.
So far so "good..." albeit not "pure." The above approach lets me see
progress on tasks as well as track planned versus actual hours. The PROBLEM
arises when/if I need to carry out major replanning. Except for the tracking
task, I no longer have planned (WORK) hours on the "real" project tasks (I
only have BASELINE WORK for those tasks) that shifts with changes in
start/finish dates, etc. For major replanning, I end up needing to move
hours BACK to the individual tasks (under WORK), make my adjustments, and
then go back through the approach discribed above. NOT something that most
people would use (some would say, waste) their time doing.
I am interested in any comments from others who may have this same issue and
how you have addressed it.
Sorry for the long post!