Domain 2 Task 6: Plan and Manage Schedule

Plan and Manage Schedule

Introduction: Why This Matters

Time is one of the most visible measures of project success. A project delivered late can erode stakeholder confidence, increase costs, and reduce business value. Planning and managing the schedule ensures that activities are logically sequenced, resources are aligned, and deadlines are realistic. It also provides the structure for monitoring progress and adjusting when variances occur.

On the PMP exam, schedule management questions often test your ability to sequence activities, apply scheduling techniques, and analyze variances. The correct answers emphasize proactive planning, monitoring, and adjustment, not shortcuts or avoidance.

Purpose and Objectives

Primary Purpose: Equip project managers with the ability to create, manage, and control schedules that support timely delivery.

Key Objectives:

  • Define activities and dependencies to create a logical flow.
  • Estimate durations using appropriate techniques.
  • Apply critical path and float analysis to prioritize work.
  • Monitor schedule performance using Earned Value and other methods.
  • Adjust schedules proactively when delays or variances occur.

Overview

Planning and managing the schedule creates a realistic roadmap for execution and a control system for staying on track.

  • Planning: Define activities, sequence work, estimate durations, and build the schedule.
  • Control: Monitor performance, analyze variances, and adjust using structured recovery options.

Characteristics

  • Logical: Activities are sequenced based on real dependencies.
  • Measurable: Progress can be tracked against a baseline.
  • Actionable: Variances trigger analysis and recovery planning.

Practical Example

Context: A construction project to build a new airport terminal is falling behind schedule. SPI is 0.85, showing significant delay.

Activities:

  • Critical path review: Identifies delayed critical path activities and confirms where recovery will actually impact the finish date.
  • Fast-tracking: Performs interior design work in parallel with ongoing structural completion where risk is acceptable.
  • Crashing: Adds additional subcontractors for finishing work to regain time on critical activities.
  • Re-baselining: Re-baselines after governance approval, with transparent communication to stakeholders.

Outcome: The project recovers several weeks, maintains stakeholder confidence, and continues with better oversight.

Common Pitfalls

Planning and Control Breakdowns

  • Pitfall: Ignoring dependencies, leading to unrealistic schedules.
  • Prevention: Confirm dependency types and validate sequencing with SMEs before baselining.
  • Pitfall: Overestimating float and assuming too much flexibility.
  • Prevention: Recalculate float after major changes and prioritize critical path work first.
  • Pitfall: Skipping monitoring and discovering delays too late.
  • Prevention: Track schedule performance routinely using trend and variance analysis.
  • Pitfall: Overusing crashing or fast-tracking, causing cost overruns or quality issues.
  • Prevention: Analyze impacts and risks before executing recovery actions.
  • Pitfall: Failing to re-baseline after major, approved changes.
  • Prevention: Re-baseline only with approval and document the reasoning clearly.

Sensei Tip : When a schedule problem appears on the exam, the first move is usually analysis. Identify the critical path, confirm the variance, then choose a recovery option.

Exam Alert : Be careful with answers that jump straight to overtime or scope cuts. The PMP exam typically expects structured schedule techniques and change control.

Exam Lens

Patterns on the PMP Exam:

  • Sequence activities using dependency types (FS, SS, FF, SF) and confirm the logic.
  • Use critical path and float analysis before selecting recovery actions.
  • Use Earned Value schedule indicators (SPI, SV) to diagnose and trend future slippage.
  • Apply fast-tracking or crashing only after evaluating risk, cost, and impact.

Sample Question

Question: A project is behind schedule. SPI is 0.8 and several critical path activities are delayed. What should the project manager do first?

  1. Add overtime for the project team immediately.
  2. Perform critical path analysis and identify recovery options such as fast-tracking or crashing.
  3. Escalate the issue to the project sponsor without analysis.
  4. Reduce scope without following change control.

Correct Answer: B. Rationale: The project manager must analyze the schedule using critical path techniques and identify structured recovery options. Overtime, escalation, or scope reduction without analysis are premature or incorrect.

Quick Recap Table

Concept Description Exam Watch Point
Critical Path Longest path through network Delay here delays project
Float Delay allowed without impact Exam may test free vs. total float
Monitoring SPI, SV, variance analysis SPI < 1.0 means behind schedule
Adjustments Fast-tracking, crashing Must analyze impact first
Pitfalls Ignoring dependencies, failing to re-baseline Avoid shortcuts

Key Takeaways

  • Effective schedule management supports on-time delivery and protects business value.
  • Critical path and float analysis guide prioritization and recovery planning.
  • Earned Value indicators (SPI, SV) provide clear performance signals.
  • Fast-tracking and crashing must be analyzed carefully for risk, cost, and quality impact.
  • The exam rewards proactive analysis and structured techniques over shortcuts.

Next Step

We will now move to Task 7: Plan and Manage Quality of Products/Deliverables, where you will learn how to integrate quality planning, assurance, and control into the project lifecycle.

Bibliography

Project Management Institute. (2021). A Guide to the Project Management Body of Knowledge (PMBOK® Guide) (7th ed.). Project Management Institute.

Scroll to Top