Schedule Management: Developing, Monitoring, and Controlling

Schedule Management: Developing, Monitoring, and Controlling

PMBOK v8 Definition

Schedule management involves the processes required to manage the timely completion of the project. It includes planning schedule management, developing the schedule model, and monitoring and controlling the project schedule to manage flexibility and meet objectives. This encompasses processes within the Planning and Monitoring & Controlling Performance Domains.

Why It Matters for the Exam

Schedule management is a core quantitative aspect of project management heavily tested on the PMI exam. Questions frequently assess your ability to interpret schedule metrics (SPI, SV), apply critical path and critical chain methods, and select appropriate schedule compression or analysis techniques in given scenarios.

Key Points to Remember (for the exam)

  • Key Process: Monitor and Control Schedule is the process where schedule performance is measured and analyzed.
  • Key Metric - Schedule Performance Index (SPI): SPI = EV / PV. An SPI > 1.0 indicates the project is ahead of schedule; < 1.0 means it's behind.
  • Key Metric - Schedule Variance (SV): SV = EV - PV. A positive SV indicates ahead of schedule; negative means behind.
  • Key Method - Critical Path Method (CPM): Identifies the longest sequence of tasks (critical path) which determines the shortest possible project duration. Tasks on this path have zero total float.
  • Key Method - Critical Chain Project Management (CCPM): A schedule method that focuses on managing remaining buffer durations and resources rather than task-level deadlines.
  • Main Focus of Control: Monitoring schedule flexibility and managing changes to the schedule baseline.
  • Common Tool: Data analysis (like Earned Value Analysis, Variance Analysis, What-if scenario analysis) is a primary tool for monitoring and controlling the schedule.

Typical PMI Exam Example

You are managing a software project. The Earned Value (EV) is $50,000, and the Planned Value (PV) is $60,000. What does this tell you about the project's schedule performance, and what is the Schedule Performance Index (SPI)?

PMI Exam Traps

  • Trap: Confusing Schedule Variance (SV) with Cost Variance (CV). Reality: SV uses Earned Value (EV) and Planned Value (PV). CV uses Earned Value (EV) and Actual Cost (AC).
  • Trap: Thinking fast tracking (doing activities in parallel) and crashing (adding resources) have the same impact on risk. Reality: Fast tracking often increases risk, while crashing typically increases cost.
  • Trap: Believing the critical path is the path with the most tasks. Reality: The critical path is the path with the longest total duration, which may have fewer tasks than a parallel path with shorter-duration tasks.
  • Trap: Assuming you should immediately act on a single SPI or SV data point. Reality: You should analyze trends and the cause of the variance before taking corrective action.

Important PMI Connections

Related ConceptRelationship TypeExam Attention Point
Scope BaselineInput to Schedule DevelopmentThe WBS and scope statement are foundational for defining schedule activities.
Risk ManagementInforms & Is Informed BySchedule risks are identified and analyzed; reserve analysis includes schedule contingency reserves.
Cost ManagementComplementary MeasurementSchedule performance (SPI/SV) is analyzed alongside cost performance (CPI/CV) for integrated Earned Value Management.
Resource OptimizationTool for Schedule DevelopmentTechniques like resource leveling and smoothing are used to develop a realistic schedule.

Quick Review Questions

  1. If a project's Schedule Performance Index (SPI) is 0.92, what is the correct interpretation?
  2. What is the primary difference between the Critical Path Method (CPM) and Critical Chain Method (CCPM)?
  3. During the "Monitor and Control Schedule" process, what is the primary purpose of using "What-if scenario analysis"?
  4. True or False: A task with positive float is always on the critical path.
  5. Which schedule compression technique typically increases risk rather than direct cost?

PMBOK v8 Reference

Section 3.7 - Schedule Performance Domain, and references within the Guide to the Processes for Schedule Management.