6.2: Schedule Management Guide

Schedule Management Guide: Overview 

Schedule management involves the processes required to manage the timely completion of the project. It includes defining, sequencing, estimating, developing, and controlling the schedule. Effective schedule management ensures the project delivers on time by providing a realistic roadmap and minimizing risks associated with delays and resource conflicts.

"A project without a clear schedule is merely a wish with a deadline."

Managing time is often the most visible aspect of project success, as every missed deadline impacts stakeholders. This chapter examines the core processes for transforming project scope into a logical, executable, and realistic roadmap that guides the entire team. By employing tools like sequencing, estimating, and Critical Path Analysis, you can prevent the "optimism trap" that often leads to project overruns.

Defining the Foundation: Defining and Sequencing Activities

Schedule management begins by defining project activities as discrete, manageable pieces of work. Defining Activities involves decomposing the work packages from the Work Breakdown Structure (WBS) into scheduled activities. Sequencing Activities then establishes the logical relationships and dependencies between these activities, determining the order in which they must be performed. This sequence identifies mandatory, discretionary, and external dependencies.

Case Study: The Invisible Dependency. "Cascade Pharmaceuticals: Clinical Trial Data Platform"

A project team assumed that an internal IT module would be ready simultaneously with the start of an external vendor's integration work. They sequenced the vendor's integration to start immediately after their module was planned to finish. They failed to realize the external vendor needed a completed, stable integration environment before they could even mobilize their team, leading to a three-month delay.

This case illustrates the critical importance of explicitly identifying all types of dependencies—especially external and discretionary ones—before finalizing the sequence.

The Project Roadmap: Developing the Schedule

After defining activities, estimating their duration, and sequencing them, the process of Developing the Schedule uses techniques like Critical Path Method (CPM) and resource optimization to produce the final schedule baseline. CPM is essential as it identifies the sequence of activities that determines the earliest completion date—the Critical Path. Any delay on a critical path activity will automatically delay the entire project. The schedule baseline, once approved, provides the fixed reference point against which actual performance is measured.

Case Study: The Path That Wasn’t Critical. "Global Logistics: Automated Sorting Facility"

A project team focused all its attention on the initial critical path identified at the start of the project. They neglected to update their analysis after a major risk event (a supplier bankruptcy) and subsequent corrective actions. By the time they realized it, a new, previously non-critical path had become critical due to accumulated delays on a set of overlooked activities.

This case highlights the necessity of dynamically monitoring the schedule to recalculate the critical path throughout the project life cycle, as delays can shift criticality to previously non-critical activities.

Keeping Pace: Controlling the Schedule

Controlling the Schedule is the ongoing effort to monitor the status of the project to update progress and manage changes to the schedule baseline. This includes determining whether the project is on track, identifying variances (deviations from the baseline), and implementing corrective actions to manage schedule risks. Tools like Earned Value Management (EVM) and variance analysis are used here to compare planned performance to actual performance and forecast future outcomes.

Case Study: The Optimism Trap. HealthSource Solutions: Patient Portal Enhancement

A project manager relied on the most optimistic estimates from team members who feared retribution for being realistic. The team consistently reported tasks as "90% complete," but the final 10% was perpetually late. The manager believed the optimistic reports until the deadline was missed, illustrating a failure of controlling the schedule due to unrealistic expectations and lack of verification.

This case demonstrates the need for project managers to be skeptical of overly optimistic estimates and to use objective data and validation, such as the 50/50 or 0/100 rules for completion, when controlling the schedule.