PMP Schedule Management: Study Guide & Exam Tips

Schedule management plans, builds, and controls the timeline: define activities, sequence them with dependencies, estimate durations, build the schedule model, and control changes to it. The exam's center of gravity is the network diagram: the critical path (longest duration path, zero total float) determines the project's earliest finish, and every scheduling decision (compression, fast-tracking, float management) flows from it. Since July 2026, schedule questions appear in both predictive clothing (network diagrams, float) and agile clothing (velocity, backlog-driven iteration planning), and hybrid scenarios blend release planning with milestone baselines.

• Critical path: the longest path through the network; it defines the project duration.
• Total float: how long an activity can slip without delaying the project. Critical-path activities have zero.
• Free float: how long an activity can slip without delaying its immediate successor.
• Lead: overlap a successor with its predecessor (start before the predecessor finishes).
• Lag: deliberate waiting time inserted between activities.
• Crashing: add resources to critical activities to shorten them; it costs more money.
• Fast-tracking: run activities in parallel that were planned sequentially; it adds risk and rework exposure.
• Critical chain: the resource-leveled path; buffers (project and feeding) protect it rather than per-activity float.

When the exam asks how to shorten the schedule, it wants you to pick between the two compression techniques and to consider their costs.

• Only critical-path activities shorten the project; compressing a path with float changes nothing.
• The best answer usually names the trade-off: crash with cost awareness, or fast-track with risk awareness, never "both" without evaluating.
• If the question mentions a hard deadline and a fixed budget, the answer often involves negotiating scope or the deadline itself rather than compressing.

• Dependency types: mandatory (hard logic: physics or law), discretionary (soft logic: preferred order), external (outside the project), internal (inside the project). Questions pair the name with a scenario.
• Estimating techniques: analogous (top-down, uses a similar past project), parametric (statistical, e.g. units × rate), three-point (PERT: (optimistic + 4 × most likely + pessimistic) / 6 for the expected value, and (P − O) / 6 for one standard deviation), bottom-up (sum the work packages; most accurate, most effort).
• PERT calculation questions are common enough to memorize both formulas before exam day.

• Velocity: story points completed per iteration; used to forecast, never as a performance target.
• Cadence: the fixed iteration length that sets the rhythm of planning, review, and retrospective.
• Backlog refinement: keeping upcoming items estimated and ready.
• Release plan: a forecast of what will be delivered by which iteration, updated as velocity data arrives.
• Kanban flow: limiting work in progress (WIP), making cycle time and throughput visible.
• Exam pattern: an agile team missing a release forecast is answered by re-forecasting from velocity and discussing scope trade-offs with the product owner, not by mandating overtime or adding people mid-iteration.

Four activities: A (3 days) starts the project, B (4 days) and C (2 days) both follow A, and D (5 days) follows both B and C.

• Path A-B-D: 3 + 4 + 5 = 12 days
• Path A-C-D: 3 + 2 + 5 = 10 days

The critical path is A-B-D, so the project needs 12 days. Activity C has 2 days of total float: it can slip two days before it delays D and the finish date. If the sponsor asks for an 11-day finish, only critical activities can help: crash B or D (adds cost) or fast-track D to overlap with B (adds risk). Shortening C changes nothing, because C is not on the critical path.

Recheck the network after every compression. Once A-B-D drops to 10 days it ties with A-C-D, both paths become critical, and any further cut must shorten both.

Delay questions reward diagnosis before action. Find the situation, then the first move:

Schedule questions sit mainly in the Process domain (41%). Business Environment (26%) supplies the reasons dates matter, such as a regulatory deadline or a market window, and People (33%) supplies the negotiations, for example with a functional manager over a shared resource.

PMI says approximately 40% of items represent predictive approaches, with the remaining 60% divided between adaptive/agile and hybrid. Expect hybrid schedules where a milestone plan for governance sits above iteration plans for the team, and rolling wave planning details near-term work while later work stays at milestone level. Network diagrams and float still matter, but so does reading a burndown chart or a release forecast and explaining what it means for the date.

• Confusing critical path (duration-driven) with critical chain (resource-driven, buffered).
• Forgetting that critical-path activities have zero total float, a favorite true/false distractor.
• Compressing non-critical activities and expecting the end date to move.
• Mixing up lead (overlap) and lag (wait).
• Treating velocity as a target to push rather than a measurement to forecast with.

Build calculation fluency before judgment fluency:

• Work network-diagram questions until finding the critical path takes under a minute.
• Memorize PERT expected value and standard deviation formulas.
• Then practice scenario selection: given a delay, what does the PM do first? (assess impact on the critical path before reacting).
• Mix predictive and agile schedule sets; the current exam interleaves them.