Task 20: Plan and Manage Schedule
Schedule management is the art of turning a vision into a timeline — and then keeping that timeline honest. ECO Task 20, the final task in the Process domain, demands that project managers estimate work realistically, structure it with milestones and dependencies, prepare schedules that match the chosen methodology, measure progress with discipline, and coordinate with other projects that compete for the same resources and attention.
This is where the rubber meets the road. A project without a credible schedule is a project that drifts. PMI tests schedule management through both quantitative methods (critical path, float, compression) and situational judgment (what to do when the schedule slips, how to handle dependencies with other projects). This guide covers every enabler thoroughly.
ECO Enablers for Task 20
The PMP Exam Content Outline structures this task around four enablers, each representing a critical competency:
- Estimate project tasks (milestones, dependencies, story points). Estimation is the foundation. Whether you're working in hours, days, or story points, the PM must be able to break work into estimable chunks, identify what those chunks depend on, and mark key milestones that anchor the schedule.
- Utilize benchmarks and historical data. PMI expects you to ground estimates in evidence — not intuition. Historical data from similar past projects, industry benchmarks, and organizational process assets provide the empirical foundation that transforms guesswork into credible planning.
- Prepare a schedule based on the methodology. The scheduling approach differs dramatically between predictive (detailed network diagrams, critical path analysis) and agile (capacity-based sprint planning, velocity-driven forecasting). The exam tests your ability to apply the right scheduling technique to the right methodology.
- Measure ongoing progress, modify the schedule as needed, and coordinate with other projects. A schedule is a living document. The PM must track actual progress against planned progress, recognize when adjustments are needed, and navigate dependencies and resource conflicts with other projects in the portfolio.
These enablers reflect PMBOK 7's emphasis on tailoring — the methodology determines the scheduling approach, not the other way around — and on the Planning and Delivery performance domains.
Estimating Project Tasks
Effective estimation begins with decomposition — breaking work into manageable, estimable pieces. The Work Breakdown Structure (WBS) is the classic predictive tool: it decomposes the project scope into work packages, which are further decomposed into activities. Each activity is then estimated for duration, resources, and cost.
In agile environments, decomposition takes the form of user stories, which are estimated in story points — a relative measure of effort, complexity, and uncertainty. Story points intentionally avoid hours-based estimation because they acknowledge that different team members work at different speeds and that uncertainty makes precise time estimates unreliable.
Dependency Types You Must Know
Dependencies define the logical relationships between activities. The PMP exam tests four types of dependencies (also called precedence relationships), and you must be able to select the right one based on the scenario:
| Dependency | Abbreviation | Meaning | Example |
|---|---|---|---|
| Finish-to-Start | FS | Activity B cannot start until Activity A finishes. The most common type — roughly 80% of all dependencies. | You must finish pouring the foundation before you can start framing the walls. |
| Start-to-Start | SS | Activity B cannot start until Activity A starts. The two activities begin together (or B starts after A begins). | You can start testing code once coding has started, even if coding isn't finished. Both activities run in parallel. |
| Finish-to-Finish | FF | Activity B cannot finish until Activity A finishes. The two activities must end together. | Quality documentation cannot be finalized until quality testing is completed. Both finish simultaneously. |
| Start-to-Finish | SF | Activity B cannot finish until Activity A starts. Rare in practice but testable. | A security guard's night shift (B) cannot finish until the morning guard's shift (A) starts. The old system must stay up until the new system is live. |
The exam often adds leads and lags to dependency questions. A lead is negative time — Activity B starts before Activity A finishes (overlap). A lag is positive waiting time — Activity B starts some time after Activity A finishes (a delay, like waiting for concrete to cure). When a scenario describes two activities happening with a waiting period or an overlap, your answer should involve applying a lag or lead to the dependency, not changing the dependency type.
Milestones and Benchmarks
Milestones are zero-duration markers that signify a significant event or achievement in the project. They don't consume resources — they mark moments: phase-gate approvals, deliverable handoffs, regulatory sign-offs, and go-live dates. PMI emphasizes milestones as communication tools: they provide stakeholders with a high-level view of progress without drowning them in activity-level detail.
Benchmarks and historical data serve a different purpose — they calibrate your estimates. If your organization has completed five website redesign projects averaging 14 weeks, and you're estimating 8 weeks for a similar scope, you'd better have a compelling explanation. PMI's message: use the data. The lessons learned register, organizational process assets, and industry benchmarks are not optional niceties — they are the foundation of defensible scheduling.
Preparing the Schedule by Methodology
How you prepare the schedule depends entirely on the methodology. The PMP exam expects you to know both worlds and — critically — not to mix them incorrectly:
In predictive (waterfall) projects, the schedule is developed through activity sequencing (creating a network diagram), estimating durations for each activity, applying the critical path method to identify the longest path (and thus the minimum project duration), and establishing the schedule baseline. The critical path is the sequence of activities with zero total float — any delay on the critical path delays the entire project. Float (or slack) is the amount of time an activity can be delayed without affecting the project finish date or an interim milestone.
In agile projects, scheduling works differently. The team defines a product backlog, estimates work in story points, establishes velocity (how many story points the team completes per sprint), and then forecasts release dates based on velocity and backlog size. There is no critical path in the traditional sense — instead, the Product Owner prioritizes the backlog to maximize value delivery, and the team self-organizes around the work within fixed-length sprints.
Measuring Progress and Modifying the Schedule
A schedule baseline is only useful if you measure performance against it. Progress measurement techniques vary by methodology but share a common principle: compare what was planned to what was actually accomplished, and use that comparison to forecast future performance.
In predictive environments, the primary tool is earned value schedule metrics (SV and SPI), percentage-complete tracking against the WBS, and milestone trend analysis. When variances appear, the PM has two primary schedule compression techniques:
| Technique | How It Works | Risks/Trade-offs | When PMI Recommends It |
|---|---|---|---|
| Crashing | Add resources to critical path activities to shorten their duration. Usually costs more money — overtime, additional staff, expedited materials. | Increases cost and risk of burnout. Only works on activities where more resources actually reduce duration (not all activities benefit). Diminishing returns apply. | When budget is available and schedule is the overriding constraint. PMI considers it the go-to technique for schedule recovery when cost isn't the primary constraint. |
| Fast Tracking | Execute activities in parallel that were originally planned sequentially. Overlaps activities that normally wait for predecessors to finish. | Significantly increases risk — rework may be required if the predecessor's output changes. Only works on activities with discretionary (soft) dependencies. | When the schedule must be compressed but the budget is tight. PMI cautions that fast tracking increases risk and should only be applied to activities with true discretionary dependencies. |
PMP candidates frequently confuse these two. The simplest distinction: Crashing = more money, same sequence. Fast tracking = same money, changed sequence (more risk). If the exam scenario says "the sponsor is willing to provide additional funds to meet the deadline," the answer is crashing. If the scenario says "the budget cannot increase but the deadline must be met," the answer is fast tracking — with an acknowledgment that risk will increase. If both are possible, PMI prefers crashing because it doesn't increase risk.
Agile Progress Measurement
In agile, progress is measured through sprint burndown charts (tracking remaining work within a sprint), release burndown charts (tracking remaining work toward a release), velocity trending (is the team's capacity stable, improving, or declining?), and cumulative flow diagrams (visualizing work-in-progress across different stages). These tools are less about schedule variance and more about forecasting based on empirical data.
Coordinating with Other Projects
Projects rarely exist in isolation. They share resources, depend on each other's deliverables, and compete for organizational attention. The PMP exam increasingly tests program and portfolio awareness — your project's schedule does not exist in a vacuum.
Key coordination practices include identifying inter-project dependencies early (especially shared resources and deliverable handoffs), participating in program-level planning sessions, using enterprise resource management systems to understand capacity across projects, and proactively communicating schedule changes that may affect dependent projects. PMI expects the project manager to look beyond their own project's boundaries and manage the intersections that could derail the schedule.
Study Checklist for Task 20
- ✅ Can you name and apply all four dependency types (FS, SS, FF, SF) and distinguish leads from lags?
- ✅ Do you understand the critical path method — how to identify the critical path and calculate float?
- ✅ Can you distinguish between crashing (add resources, increase cost) and fast tracking (parallel execution, increase risk)?
- ✅ Do you know how scheduling approaches differ between predictive (network diagrams, critical path) and agile (story points, velocity, burndown charts)?
- ✅ Are you able to describe how to use benchmarks and historical data to validate schedule estimates?
- ✅ Do you understand how to coordinate schedules across multiple projects and manage inter-project dependencies?
Task 20 closes out the Process domain with the discipline that ties everything together: scheduling. A well-managed schedule integrates scope, budget, resources, risk, and stakeholder expectations into a single coherent timeline. Master these concepts, and you'll be prepared for the scheduling questions that appear in both the Process domain and throughout the full PMP exam. Return to the ECO Study Guide Index to review other tasks or practice Process Domain questions.
← Back to ECO Study Guide Index | Practice Process Domain Questions →