Schedule
The schedule domain focuses on defining, sequencing, estimating, and controlling project activities and milestones so that the project objectives are achieved within agreed timeframes.
Why this domain matters
The schedule turns ideas and scope into a realistic plan for when work will happen. A well-built schedule helps manage expectations, coordinate resources, and reveal the impact of changes and risks. Weak schedules lead to constant fire-fighting, unrealistic deadlines, and repeated slippage that damages credibility with stakeholders.
Key concepts
- Activities and milestones: the detailed tasks and key points that structure the work.
- Dependencies: logical relationships between activities (finish-to-start, start-to-start, etc.).
- Critical path: the longest sequence of activities that determines the project finish date.
- Float (slack): the amount of time an activity can be delayed without affecting the project end date.
- Schedule baseline: the approved version of the schedule used for performance measurement.
Common pitfalls and exam traps
- Building a schedule directly from tasks without confirming scope and deliverables first.
- Using overly optimistic estimates and ignoring uncertainty and risk.
- Not maintaining the schedule, leading to outdated or meaningless dates.
- Focusing on percentage complete instead of critical path and milestone performance.
- Exam trap: choosing to “add resources” or “work overtime” without first analyzing the critical path and constraints.
PMP Example Question
PMP Example Question
The sponsor asks the project manager to shorten the project duration by two weeks without reducing scope. After reviewing the schedule, the project manager confirms that the critical path is driving the finish date. What is the most appropriate technique to consider first?
- Leveling resources across noncritical activities.
- Crashing activities on the critical path that can be shortened at additional cost.
- Increasing overtime on all project activities.
- Adding leads to all activity relationships.
Correct Answer: B — Crashing activities on the critical path that can be shortened at additional cost.
Explanation: When the finish date must be brought forward and scope is unchanged, schedule compression techniques such as crashing and fast tracking are used. Crashing focuses on activities on the critical path where additional resources or cost can reduce duration. Resource leveling usually lengthens the schedule, and increasing overtime or adding leads everywhere is uncontrolled and may introduce risk and rework.
