The purpose of the Direct and Manage Project Execution process is to carry out the project plan. This is where your project comes to life and the work of the project happens. The work is authorized to begin and activities arc performed. Resources arc committed and carry out their assigned activities to create the product or service of the project. Funds arc spent to accomplish project objectives. Performing project activities, training, selecting sellers, collecting project data, utilizing resources, and so on arc all integrated with or a part of this process.
Direct and Manage Project Execution is where the rubber meets the road. If you've done a good job planning the project, things should go relatively smoothly for you during this process.
Executing Inputs
Direct and Manage Project Execution has seven inputs:
• Project management plan
• Approved corrective actions
• Approved preventive actions
• Approved change requests
• Approved defect repair
• Validated defect repair
• Administrative closure procedure
The project management plan documents the collection of outputs of the Planning processes and describes and defines how the project should be executed, monitored, controlled, and closed. We'll take a brief look at each of the other inputs next.
Approved Corrective Actions
In my organization, a corrective action means an employee has big trouble coming. Fortunately, this isn't what's meant here. Corrective actions arc taken to get the anticipated future project outcomes to align with the project plan. Maybe you've discovered that one of your programmers is adding an unplanned feature to the software project because he's friends with the user. You'll have to redirect him to the activities assigned to him originally to avoid schedule delays. Perhaps your vendor isn't able to deliver the laboratory equipment needed for the next project phase. You'll want to exercise your contract options (hopefully there's a clause in the contract that says they must provide rental equipment until they can deliver your order), put your contingency plan into place, and get the lab the equipment that's needed to keep the project on schedule.
Direct and Manage Project Execution is where the rubber meets the road. If you've done a good job planning the project, things should go relatively smoothly for you during this process.
Executing Inputs
Direct and Manage Project Execution has seven inputs:
• Project management plan
• Approved corrective actions
• Approved preventive actions
• Approved change requests
• Approved defect repair
• Validated defect repair
• Administrative closure procedure
The project management plan documents the collection of outputs of the Planning processes and describes and defines how the project should be executed, monitored, controlled, and closed. We'll take a brief look at each of the other inputs next.
Approved Corrective Actions
In my organization, a corrective action means an employee has big trouble coming. Fortunately, this isn't what's meant here. Corrective actions arc taken to get the anticipated future project outcomes to align with the project plan. Maybe you've discovered that one of your programmers is adding an unplanned feature to the software project because he's friends with the user. You'll have to redirect him to the activities assigned to him originally to avoid schedule delays. Perhaps your vendor isn't able to deliver the laboratory equipment needed for the next project phase. You'll want to exercise your contract options (hopefully there's a clause in the contract that says they must provide rental equipment until they can deliver your order), put your contingency plan into place, and get the lab the equipment that's needed to keep the project on schedule.