6.7 Control Schedule
The Control Schedule process monitors the progression of the project against the established schedule and manages adjustments through the change process to accomplish the planned project outcomes. I affords a means to recognize deviations and plan for corrective actions to minimize adverse risks. The Inputs, Tools & Techniques and Outputs for this process are listed below.
Figure 40. Manage Stakeholder Engagement: Inputs, Tools & Techniques, and Outputs. Reprinted from "A Guide to the Project Management Body of Knowledge (PMBOK Guide), 5th Edition" by Project Management Institute, 2013, p.185. Copyright 2013 by Project Management Institute, Inc. Reprinted without permission.
In the Control Schedule process the project schedule is monitored and updated. Any changes to the schedule must proceed through the Perform Integrated Change Control Process. This make certain that all appropriate documents are updated and stakeholders notified.
As part of the integrated control process things to consider while performing the Control Schedule process are:
- The current schedule and project progress
- Factors that may cause schedule deviation
- Identify any schedule changes that have occurred
- Overseeing the changes through the process as they happen
This Nighting Gale case study, From PMGT 501, was introduced in an earlier process in this artifact I've included the schedule data for the original project which will not meet a deadlines set to a preempt a competitors first to market plans on a similar product. See 6.7.1
Tools & Techniques
The tools and techniques used to correct the Nighting Gale case study dilemma were a change to the original lead lag time and moving a few start to finish schedules to a start to start to start schedule. The cost of the move are included in the analysis. See 6.7.2
The final artifact is a proposed schedule forecast follow a crashing procedure don't in PMGT501 sustainable home project. This process would be included in the Project Management plan in an update as it was approved. See 6.7.3