6.3: Chapter Summary

Conclusion

This guide has provided the tools necessary to move beyond simple task lists and into the rigorous discipline of professional schedule management. By mastering the processes of defining, sequencing, and estimating work, you gain the ability to predict the future of your project including its duration, its risks, and its most critical path. The goal is not merely to meet deadlines, but to establish a realistic, shared, and controlled roadmap that transforms uncertainty into measurable predictability.

Think about your current project. What is the single longest dependency chain currently driving your project's completion date? If you had to increase the speed of your project, would you use fast-tracking (overlapping activities) or crashing (adding resources)? Reflect on your last schedule delay. Was the root cause a poor initial duration estimate, an unrecognized dependency (The Invisible Dependency), or a resource conflict? Do a tools check. Do you use the Critical Path Method (CPM) to focus attention on the few activities that truly matter, or do you treat all tasks with equal urgency?

Schedule is never cast in stone

One common misconception is that the schedule, once approved and baselined, is a static document. In reality, the schedule is a dynamic tool for managing time. A major warning sign is when a project manager focuses solely on tracking progress against the original Schedule Baseline without actively recalculating the Critical Path. As the The Path That Wasn’t Critical case study showed, this can lead to a critical path shift, where a previously non-critical task accumulates delays and suddenly threatens the entire project without warning. True schedule control is about constant vigilance, adapting to changes, and ensuring the team is always focused on the currently most time-sensitive work.1

These reflections will help apply and internalize the concepts learnt in this chapter. 

Key Terms to Remember

• Schedule Management Plan: A document defining how the schedule will be developed, monitored, and controlled.
• Activity: A specific task derived from WBS work packages that consumes time and resources.
• Milestone: A significant point or event in the project with zero duration.
• Precedence Diagramming Method (PDM): A technique for creating network diagrams showing activity dependencies.
• Finish-to-Start (FS): A dependency where the successor cannot start until the predecessor finishes.
• Lead Time: An acceleration of the successor activity, allowing it to start before the predecessor finishes.
• Lag Time: A delay between the predecessor and successor activities.
• Critical Path: The longest sequence of dependent activities that determines minimum project duration.
• Float (Slack): The amount of time an activity can be delayed without affecting project completion.
• Three-Point Estimate: An estimation technique using optimistic, pessimistic, and most likely values.
• PERT Formula: Expected duration = (Optimistic + 4×Most Likely + Pessimistic) ÷ 6.
• Crashing: Adding resources to critical path activities to reduce duration, increasing cost.
• Fast-Tracking: Overlapping activities that would normally be sequential, increasing risk.
• Resource Leveling: Adjusting the schedule to resolve resource overallocation, often extending duration.
• Schedule Variance (SV): Earned Value minus Planned Value; negative values indicate behind schedule.
• Schedule Performance Index (SPI): Earned Value divided by Planned Value; values below 1.0 indicate inefficiency.
• Velocity: An agile metric measuring the amount of work a team completes per iteration.