mr b said:
John,
Thanks for the response. We are looking more for the linear reduction type
of capabilities. I should have explained more...
I have done this in the past using MS Excel. I do up the entire workplan in
Excel. The estimate for each task is based on hours per unit and the number
of units. The number of units is based on the scope of the project. The
number of units (in this case, programs) is stored in one cell and then
re-used across multiple tasks. This way, if we adjust the scope (and thus
the number of units/programs), the spreadsheet automatically readjusts the
total work effort and voila', in one second we have the answer to how much
the effort changes because of the scope change. I use from 50 to 100 such
unit types (we call them estimating factors) in a typical workplan. The
limitation is that Excel requires that we manually re-schedule the project,
which can take hours. We are hoping to leverage MS project for the task
dependencies and scheduling capabilities but we don't want to lose the
ability to make quick adjustments to the effort levels on the tasks like we
have done in Excel.
Can you think of a quick way to readjust the effort similar to the way we
have been doing it in Excel?
By the way, once we have settled on a scope and an overall estimate, we
would then start developing detailed workplans with each program listed and
detailed dependencies, resources, etc.
Mr b,
I can think of a couple of ways to implement Project to do the
equivalent of what you currently do in Excel. One is through the use of
one or more formulas in custom fields and the second is via VBA. I
rarely use formulas because they have many limitations and can get very
complex in a hurry. If I were to implement what you want I would write a
macro based on this pseudo-code.
1. Pop up a user message asking for the number of units
2. Set up a loop to cycle through all tasks (or a specific set of tasks).
3. Perform whatever units/program math you need to adjust the task work
4. End of story, you're done
Keep in mind that in Project Task Duration and Task Work are two
different things. Duration is the time span estimated for completing the
task. Work is the effort of one or more resources to perform the task.
For example, an estimate of 1 week (40 hours duration) may be given for
writing a code module. However the effort of a single resource to
perform the task may only be 30 hours (Work effort). Your post talks
about "work effort" so the pseudo-code above assumes you want to adjust
the Work field. In a plan that has more than one resource per task
things can get a little more complex unless all resources on that task
have equal work.
Hope this helps.
John
Project MVP