8.4 Managing the Schedule
Visit Audio Recordings for the audio version of this section.
- Describe methods of tracking and reporting progress.
- Define resource leveling.
- Describe methods of accelerating the schedule.
To manage a schedule, the project manager must know how the work is progressing compared to the master schedule and, if necessary, make changes to keep the project on time.
TRACKING AND REPORTING PROGRESS
Tracking the schedule performance involves measuring the work performed against the work expected to be performed with a given expenditure of resources. Periodic reporting on the progress of the project provides the project management team with information on how the project is performing against expectations and to make decisions and corrections. Accurate measurement of schedule performance requires planning during the early stages of the project to determine the unit of measure and process for tracking progress.
Reporting Percentage Completed
To determine the percentage of a project that has been completed, the project manager must determine what to measure. Some percentages are misleading. For example, a project that has completed 25% of the scheduled activities does not mean that the project is 25% complete. In our John’s move example, four rooms were to be packed. After the bedroom was packed, packing was not 25% complete. The kitchen contained five times as many items and required more delicate, time-consuming packing. John estimated that 40% of the items to be packed were in the kitchen, 20% in the living room, 20% in the bedroom, and the remaining 20% in miscellaneous locations. If the unit of measure for these activities is items packed, the packing is only 20% complete instead of 25% if rooms are the unit of measure.
The unit of measure for tracking schedule progress is related to the estimate. If hours of labor are used as the unit of measure, the percentage of packing is even less because more time is estimated to pack each item in the kitchen. As the project management team estimates the duration for each activity, the amount of work to accomplish the tasks is captured in both resources expended and a unit of measure for tracking progress. The unit of measure is related to the type of project. On a software development project, the unit of measure may be lines of code written. The unit of measure that is chosen can affect the quality of the work.
Units of Measure on a Programming Project
Steve Ballmer of Microsoft related early clashes with IBM over the unit of measure used to determine how much Microsoft would get paid for its work for IBM. IBM’s standard was to pay per K-LOC, which is a thousand lines of code; Microsoft thought that they should not be paid less if they were able to produce good work in fewer lines of code.1
In this case, IBM’s insistence on using thousands of lines of code as the unit of measure did not reward Microsoft for writing smaller code that would run faster. Microsoft and IBM cancelled their joint project for writing an operating system named OS/2. Microsoft wrote Windows, and IBM’s OS/2 operating system was not able to compete with it successfully.
On a construction project, a unit of measure may be yards of concrete poured, and on a training project, the unit of measure may be the class curriculums developed or the number of students taught.
Managing Schedules Using Milestones
Milestones provide the opportunity for project management to focus on completing activities that will have the greatest impact on the schedule. On complex projects, focusing on the milestones is useful for communicating important dates to the entire project team. Project team members can then adjust their efforts to complete the activities connected to the milestone events.
Many project leaders believe that time lost on early activities can be made up toward the end of the project. Hard decisions about paying overtime and working weekends are often delayed until the end of the project when the pressure to complete the project on time becomes much stronger. Project managers who focus on milestone events create a sense of urgency to meet the milestone deadlines and spread the urgency to complete the project over the life of the project. Projects that meet milestone dates are more likely to meet project completion dates.
A schedule update is distributed regularly to provide project stakeholders with an assessment of the progress of the project against the master schedule. This updated schedule is called the current schedule. The current schedule provides new start and end dates for all activities and the project. Calculations based on the current schedule may result in a new critical path and subsequent changes in the project execution plan.
The project team develops an understanding of the project productivity by comparing the current schedule to the original schedule. If the schedule is behind original estimates, the project team conducts an assessment of the causes of the schedule slippage and develops a plan to address the changes to the project. The project management team typically has several alternatives for addressing changes to the project situation. Selecting the right alternative requires good information.
The schedule of activities is constrained by the availability of resources. If you apply the resource calendar to each activity to be sure the people and equipment are available on those dates, you can still miss an important constraint. If there are several activities that use a particular person’s time on the same days, that person could end up with too many activities scheduled for the same days and very little on other days. If key people are overloaded, the activities to which they are assigned might not be completed on time. Managing the schedule of activities to ensure that enough resources are available to complete each task by distributing the work load is called resource leveling. Activities to which that person is assigned and that have free float can be delayed to reduce work overload of key people.
ACCELERATING THE SCHEDULE
The project manager must know how to accelerate a schedule to compensate for unanticipated events that delay critical activities or to accommodate changes in the project completion date. Compressing or crashing the schedule are terms used to describe the various techniques used to shorten the project schedule. Project managers utilize several techniques to keep projects on schedule.
One method of accelerating the schedule is to add activities to the critical path that are empty or that are optional. If the project is behind schedule, the time can be made up by dropping these activities. This extra time that is built into the schedule is called contingency time, buffer, or reserve time.
Activities that are not on the critical path that have free float can be delayed without delaying the end date of the project if they start by the late start date. Project managers can divert some resources from activities with free float to activities on the critical path without delaying the completion of the project.
The unit cost of work to be performed on a project is calculated at the beginning of the project based on the execution strategy of the project to meet the project completion date. If the project completion date is moved up, then the unit cost of work will likely increase. Conversely, a project team may be able to save money by extending the project end date. With more time, the project team may be able to schedule activities in such a way to reduce their costs. For example, an activity requiring overtime to be paid can now pay the labor at normal rates, saving the overtime premium. Changing elements of the master schedule means a change in scope. Scope changes often affect costs and require agreement by the parties who signed the original scope documents.
Another option is to allocate funds that can be used to add resources if necessary. Available resources can be increased by adding overtime to existing resource calendars or by hiring additional contract workers or renting additional equipment.
Adding Resources to the Dreamliner Project
When Boeing sales of the new 878 Dreamliner Airplane exceeded expectations, contractors who were building the plane were asked to increase production while maintaining all quality and safety requirements. All contractors involved in the plane production were affected by this change.
One project team was responsible for developing and delivering training to the new employees who would be building the fuselage of the Dreamliner. Training for new employees had to be complete three months early and the project team developed an execution strategy to meet the new deadlines. The project had a month of float, so the project accelerated the schedule by two months. The team authorized overtime from forty to fifty hours a week for team members working activities on the critical path. The project team leased additional space and hired contractors to perform selected work packages on the critical path and delayed the production of library quality documents until after the critical dates on the project. Authorizing overtime and hiring contractors added a 15% cost to the project. Overtime and the procurement of additional contract help was authorized only for work packages on the critical path because work not on the critical path would not accelerate the schedule.
Another option for accelerating the schedule is the changing of the quality specifications of the product. This is usually done as a scope change.
Making Up Time by Reducing Quality
A western university contracted an online learning company to make an online independent study course for their Calculus 112 class. As the project went on it fell behind schedule. To speed up the project, it was decided to produce fewer animated videos, which meant that some of the lessons would not have these learning aids. The contract did not specify the amount or quality of these videos so this change did not require a change of scope. As a result, some of the more difficult calculus principles had only text as instruction. The university did not realize this change had been made until after the project was completed and being used by the students.
- Progress can be measured by determining the percentage of resources expended, completion of activities by scheduled dates, milestones achieved, or fraction of activities accomplished. Standards used to measure progress, particularly when partial payment to contractors is concerned, should be specified in contract documents.
- Resource leveling is reallocating people and equipment to remove periods of overuse or underuse.
- Unplanned delays and costs can be anticipated by including contingency time and budget amounts where needed to keep the schedule on time. Resource allocation and resource calendars should be examined to determine if a resource is overcommitted. Free float can be used to delay noncritical activities that use the same resource to allocate its time more evenly. If it is necessary to accelerate the schedule, activities that are not on the critical path can be delayed using their free float and their resources can be moved to activities on the critical path to complete them sooner. Contingency resources can be committed to speeding up the activities. If necessary, the scope can be changed to bring in additional resources or lower the quality.
 Robert X. Cringely, Triumph of the Nerds, June 1996, http://www.pbs.org/nerds/part2.html (accessed July 27, 2009).