PMP Schedule Management: Practice Questions & Exam Prep

Schedule management on the PMP covers planning the schedule, defining activities, sequencing activities, estimating durations, and developing and controlling the schedule. You need to understand key outputs (schedule baseline, network diagram, critical path) and tools (e.g. critical path method, schedule compression).

Activities are sequenced with dependencies (finish-to-start, start-to-start, etc.); duration estimates feed into the schedule; the critical path is the longest path and determines the minimum project duration. Compression techniques (crash, fast track) can shorten the schedule but may add cost or risk.

Common traps include confusing “critical path” with “critical chain,” or forgetting that the critical path has zero float. Another trap is applying fast track or crash without considering impacts. Float and slack are also frequently tested—know how they’re calculated and who “owns” float in different contract types.

Use PMP Exam Lab to practice schedule questions in the Process domain. Focus on “what is the critical path?” and “what should the PM do to compress the schedule?” and review the explanations to lock in the concepts.

Frequently Asked Questions

What is the critical path?
The critical path is the longest path through the project network and determines the shortest possible project duration. Activities on the critical path have zero total float; any delay to them delays the project.
What’s the difference between fast track and crash?
Fast tracking is compressing the schedule by doing activities in parallel that were originally sequential (can add risk). Crashing is adding resources to critical path activities to shorten duration (can add cost).
Who owns float?
In many contracts, total float is shared; in others it may be assigned to the owner or the contractor. The PMP exam often expects you to understand that float is a shared buffer and that the critical path has zero float.
What is float and how is it calculated?
Total float (slack) is the amount of time an activity can be delayed without delaying the project end date. It is calculated as late finish minus early finish (or late start minus early start). Activities on the critical path have zero total float. Free float is the delay possible without affecting the early start of any successor.
What is schedule compression and when do you use it?
Schedule compression shortens the project duration without changing scope. Fast tracking does activities in parallel (increases risk). Crashing adds resources to critical path activities (increases cost). Use when the schedule must be shortened; choose based on whether risk or cost is more acceptable.
What is resource leveling and how does it affect the schedule?
Resource leveling adjusts the schedule to address resource over-allocation, often by delaying non-critical activities. It may extend the project end date. Resource smoothing adjusts within available float and does not extend the schedule. PMP questions often test when to use leveling vs. smoothing and the impact on the critical path.