⏱️ Schedule Management
Study Notes — Page 3 | ClearPMPExam.com
1. What is Schedule Management?
Schedule Management is the process of planning, developing, managing, executing, and controlling the project timeline — ensuring the project is completed on time.
Think of Schedule Management as your project’s calendar engine. It answers: What tasks need to be done? In what order? How long will each take? What is the earliest date we can finish? And what happens if a task is delayed?
🏥 Real Example — Pharma App Launch
A pharma company wants to launch a patient engagement app before World Diabetes Day (November 14). Schedule Management means: breaking the launch into tasks (design, development, testing, compliance review, go-live), sequencing them in the right order, estimating how long each takes, finding the fastest possible path to launch, and tracking progress week by week.
👉 Without schedule management, tasks happen in random order and the launch date is missed.
2. The 6-Step Schedule Process — In Order
Like scope, schedule management follows a fixed sequence of steps. The exam tests whether you know what happens at each step and what it produces.
Plan Schedule Management
Decide how the project schedule will be created, maintained, and controlled. Sets the rules for everything that follows.
Output → Schedule Management PlanDefine Activities
Convert WBS work packages into specific, actionable tasks. This is where you go from “what to deliver” to “what actions to take.” Activity = smallest unit of schedulable work.
Output → Activity List, Activity Attributes, Milestone ListSequence Activities
Determine the logical order of activities. Identify dependencies — which tasks must finish before others can start. Uses the Precedence Diagramming Method (PDM) where activities are nodes and arrows show dependencies.
Output → Project Network Diagram, Updated Activity ListEstimate Activity Durations
Estimate how long each activity will take. Uses techniques like Analogous, Parametric, Bottom-Up, and Three-Point (PERT) estimation. Resource availability affects these estimates.
Output → Duration Estimates, Basis of EstimatesDevelop Schedule
Combine the activity list, duration estimates, and network diagram to build the actual project timeline. Calculates start/finish dates for all activities. Uses Critical Path Method, resource levelling, and schedule compression if needed.
Output → Schedule Baseline, Project Schedule, Schedule DataControl Schedule
Track actual progress against the schedule baseline. Identify variances, manage changes, and take corrective action when tasks are running behind. Uses Earned Value Management (SPI).
Output → Work Performance Information, Change Requests, Schedule Forecasts“Plan → Define → Sequence → Estimate → Develop → Control” = “Please Do Some Extra Delicious Cake”
3. Critical Path Method (CPM) — Most Tested Concept
The Critical Path is the longest sequence of dependent activities in the project network. It determines the minimum possible project duration. Any delay on the critical path = delay to the entire project.
Imagine your project as a series of roads connecting start to finish. Some roads have delays and detours, some are fast. The critical path is the longest road — and since every other route is shorter, the project cannot finish any faster than this longest route takes.
START
Design
5 days
Content
7 days
Review
3 days
Launch
2 days
END
Critical path is about TIME, not importance. A task can be critical (on the critical path) even if it seems minor. What makes it critical is that delaying it delays the entire project — not how important the task is.
Key rule: Activities on the critical path always have zero float (zero slack). If a question asks “which activity has zero float?” — the answer is always a critical path activity.
4. Float (Slack) — Total Float vs Free Float
Float is the amount of time an activity can be delayed without causing problems. There are two types — and the exam tests both, often in the same question.
🔵 Total Float
How long an activity can be delayed without delaying the entire project end date.
Example: If a task has 3 days of total float, it can slip by up to 3 days and the project will still finish on time.
Critical path activities always have Total Float = 0.
🟢 Free Float
How long an activity can be delayed without delaying the start of the very next activity.
Example: If a task has 2 days of free float, it can slip by 2 days and the next task can still start on its planned date.
Free Float is always ≤ Total Float.
Total Float = delay without hurting the PROJECT. Free Float = delay without hurting the NEXT TASK. Total is bigger. Free is smaller and more specific.
5. Dependencies — How Tasks Relate to Each Other
Before you can sequence activities, you must understand how tasks depend on each other. The exam gives scenario descriptions and asks you to identify the dependency type.
| Dependency Type | Meaning | Example | Most common? |
|---|---|---|---|
| Finish-to-Start (FS) | Task B cannot start until Task A finishes | Testing cannot start until coding finishes | ✅ Most common |
| Finish-to-Finish (FF) | Task B cannot finish until Task A finishes | Testing cannot finish until development finishes | Less common |
| Start-to-Start (SS) | Task B cannot start until Task A starts | Documentation can start once coding starts | Less common |
| Start-to-Finish (SF) | Task B cannot finish until Task A starts | Old system can’t be shut down until new one starts | Rare |
When a question says “Task B can only begin after Task A is done” — that is Finish-to-Start (FS). This is the default and most common dependency. When in doubt, FS is almost always the answer.
6. Schedule Compression — Crashing vs Fast Tracking
The project is running late. The deadline cannot move. How do you speed things up? There are exactly two techniques the PMP recognises — and the exam loves to test them together.
Crashing — Add Resources
What it means: Add more people, equipment, or money to a task to finish it faster.
Real example: A coding task takes 10 days with 1 developer. Add 2 more developers → now done in 4 days.
Only works on: Critical path activities. Adding resources to non-critical tasks is a waste of money.
Fast Tracking — Overlap Tasks
What it means: Do tasks in parallel that were originally planned to be done in sequence.
Real example: Normally: Design finishes → then Development starts. Fast tracking: Start Development while Design is still 70% done.
No extra cost — but high risk of rework if earlier task changes after later task has started.
“Add more resources / overtime / extra budget to finish faster” → Crashing.
“Overlap tasks / do in parallel / start before previous finishes” → Fast Tracking.
“Compress without increasing cost” → Fast Tracking (only option with no cost increase).
“Resource shortage / overallocation” → Resource Leveling (not compression).
7. Resource Optimization — Leveling vs Smoothing
Sometimes the schedule is technically correct but resource-impossible — one person is assigned to 4 tasks on the same day. Resource optimization fixes this. Two techniques, very different impacts.
🔴 Resource Leveling
Adjust the schedule based on resource availability. If a resource is overloaded, shift tasks to later — even if it delays the project.
Impact: May delay the project end date.
Use when: Resource availability is the hard constraint and the deadline is flexible.
Example: 1 designer is assigned to 2 tasks simultaneously. Shift one task to next week. Project end date moves by 5 days.
🟢 Resource Smoothing
Adjust tasks within their float — without delaying the project. Only adjusts non-critical activities.
Impact: Project end date does NOT change.
Use when: The deadline is fixed and you want to balance resource usage within the available float.
Example: A task has 3 days of float. Shift it 2 days later to free up a resource — project still finishes on time.
Leveling = delay allowed (L = Longer project). Smoothing = no delay (S = Same end date). When you see “resource conflict” in the exam — Leveling. When you see “within float” — Smoothing.
8. Estimation Techniques — The 4 You Must Know
Before you can build a schedule, you need to estimate how long each activity takes. The PMP exam tests four main estimation techniques. Know which is fastest, which is most accurate, and what triggers each one in a question.
Analogous Estimating
Use data from a similar past project to estimate the current one. Relies on expert judgment and historical records.
Example: “Last pharma website took 30 days → this one will take about 30–35 days.”
Fast Less accurateParametric Estimating
Use a formula or rate multiplied by quantity. Statistical relationship between variables.
Example: ₹1,000 per page × 10 pages = ₹10,000. Or: 2 hours per module × 8 modules = 16 hours.
Fast Medium accuracyBottom-Up Estimating
Estimate each individual task, then add them all up to get the total. Starts from the lowest level of the WBS.
Example: Task A = 2 days, Task B = 3 days, Task C = 5 days → Total = 10 days.
Time-consuming Most accurateThree-Point (PERT)
Use three scenarios — Optimistic (O), Most Likely (M), Pessimistic (P) — to calculate a weighted average that accounts for uncertainty.
Example: O=3, M=5, P=10 → E = (3 + 4×5 + 10) ÷ 6 = 5.5 days
High accuracy Handles uncertainty“Based on similar past project” → Analogous. “Formula / rate × quantity” → Parametric. “Estimate each activity and sum up” → Bottom-Up. “Optimistic, most likely, pessimistic” → Three-Point / PERT.
9. The PERT Formula — Learn It, Never Forget It
PERT (Program Evaluation and Review Technique) is the three-point estimation formula. It gives a weighted average that leans toward the most likely estimate, while still accounting for best and worst cases.
EXPECTED DURATION
STANDARD DEVIATION
🧮 Worked Example — Exam Style
Task: UI Design for a new health app
Optimistic (O) = 3 days | Most Likely (M) = 6 days | Pessimistic (P) = 15 days
Expected Duration: E = (3 + 4×6 + 15) ÷ 6 = (3 + 24 + 15) ÷ 6 = 42 ÷ 6 = 7 days
Standard Deviation: SD = (15 − 3) ÷ 6 = 12 ÷ 6 = 2 days
This means we are 68% confident the task will take between 5–9 days (7 ± 2), and 95% confident it takes between 3–11 days (7 ± 4).
The Most Likely estimate gets 4× weight because reality is usually closest to the most likely scenario. Optimistic and Pessimistic each get 1× weight. The formula is a weighted average, not a simple average.
10. Other Important Schedule Tools
Gantt Chart
Bar chart showing all activities on a timeline. Shows start/end dates, duration, and overlap. The most widely used schedule visualisation tool.
Network Diagram (PDM)
Activities shown as boxes/nodes, arrows show dependencies. Used to identify the critical path and calculate float.
Rolling Wave Planning
Plan near-term work in detail, keep future work at a high level. As the project progresses, future work is planned in more detail. Used when full scope is not yet clear.
Monte Carlo Simulation
Runs thousands of schedule simulations using probability ranges to predict likely project completion dates. Answers: “What is the probability we finish by date X?”
Critical Chain Method (CCM)
Like CPM but also considers resource constraints. Adds buffers to protect the schedule: Project Buffer (end), Feeding Buffer (before joining critical chain), Resource Buffer (ensures availability).
Milestones
Key checkpoints in the schedule with zero duration. They mark significant achievements: “Design approved,” “Beta released,” “App launched.” No work — just a marker.
11. Quick Summary Table — Everything at a Glance
| Concept | One-line meaning | Exam trigger word |
|---|---|---|
| Critical Path | Longest path = minimum project duration | “longest path” / “zero float” |
| Total Float | Delay without delaying the project end date | “how long can this be delayed” |
| Free Float | Delay without delaying the next activity | “without affecting the next task” |
| Crashing | Add resources to reduce duration, cost goes up | “add resources” / “overtime” |
| Fast Tracking | Overlap tasks, no extra cost, risk goes up | “overlap” / “parallel” / “no extra cost” |
| Resource Leveling | Fix overallocation — may delay project | “resource conflict” / “overallocated” |
| Resource Smoothing | Fix within float — no delay to project | “within float” / “no delay allowed” |
| Analogous | Use past project data — fast, less accurate | “similar past project” |
| Parametric | Formula: rate × quantity | “formula” / “rate per unit” |
| Bottom-Up | Estimate each task and add up — most accurate | “estimate each activity” / “most accurate” |
| PERT / Three-Point | (O + 4M + P) ÷ 6 — handles uncertainty | “optimistic / pessimistic / most likely” |
| Rolling Wave | Plan near work in detail, far work high-level | “progressive elaboration” / “not fully known yet” |
| Monte Carlo | Simulate thousands of outcomes using probability | “probability” / “simulate” / “range of outcomes” |
🎯 Practice Q&A — Test Yourself
Think of your answer first. Then click to reveal.
✅ Page 3 complete. Next up: Page 4 — Cost Management & Earned Value — EVM formulas, CPI, SPI, EAC, and worked examples step by step.