Executing
There are two aspects to the process of project execution. One is
to execute the work that must be done to create the product of
the project. This is properly called technical work, and a project is
conducted to produce a product. Note that we are using the
word “product” in a very broad sense. A product can be an actual
tangible piece of hardware or a building. It can also be software
or a service of some kind. It can also be a result—consider, for example
a project to service an automobile that consists of changing
the oil and rotating the tires. There is no tangible deliverable for
such a project, but there is clearly a result that must be achieved,
and if it is not done correctly the car may be damaged as a result.
Executing also refers to implementing the project plan. It is
amazing to find that teams often spend time planning a project,
then abandon the plan as soon as they encounter some difficulty.
Once they do this, they cannot have control of the work, since
without a plan there is no control. The key is to either take corrective
action to get back on track with the original plan or to revise
the plan to show where the project is at present and
continue forward from that point.
