The only controls you have on the critical path are indirect controls where
the path is affected by the decisions you have made regarding task
sequencing and their durations if, and that's a very big "if," you can
actually control the duration. IF a painter can apply paint at a maximum
rate of 10 square feet of wall per hour, you have 250 square feet of wall to
paint, and only one painter to do it with, that pretty well puts that task
duration out of your control - it's going to be mighty close to 25 man-hours
of effort required and the duration will be 25 working hours if the painter
is fully committed and more than that if he only can devote part of his
energy to that specific task.
As Mike said, there is no difference in deleting a task on the critical path
from deleting one that's not on the critical path - you simply delete it.
Adding a task is equally simple but it may or may not end up a critical task
or on the critical path. IMHO, task linkages are dictated by the nature of
the physical processes involved in creating the task deliverables. Erecting
walls is a predecessor to installing rafters not because we want to
structure the work that way but rather because the law of gravity doesn't
give us the option of setting the rafters in midair and then stuffing the
walls in under them later. Another rule is that all tasks in the project
will have at least one predecessor and one successor, except for the start
and the end milestones. If a task has no other direct successor, it will
still have the finish milestone linked to it. When your project is
structured like that you will find there are usually multiple paths leading
from the start to the end - one of them will be the longest of the
alternatives and that is the critical path by definition. If the task
you're adding belongs in that sequence due to the nature of the deliverable
inputs it requires and the outputs it produces, it will add to the critical
path. If it doesn't fit into that sequence of operations according to the
nature of the physical process itself, then it doesn't add to the critical
path. That's why I say you don't choose it - the structure of the project
is pretty well something that is dictated by the nature of the work
processes and as a PM part of our job is to discover the most efficient way
of getting it done. Notice the operative word is "discover." It is a
process of discovery, not an imposition of our will. Our will comes into
play when we're defining the goals but once we decide what we want to
achieve, we then discover the best way of achieving them.
--
Steve House [MVP]
MS Project Trainer & Consultant
Visit
http://www.mvps.org/project/faqs.htm for the FAQs