Guide §2.3 · PRINTED PP. 47–57
Schedule Performance Domain
Schedule management turns the intended scope into a time-based model for delivery, communication, forecasting, and control. The schedule is not merely a date list: it links activities through logic, assigns durations and resources, exposes constraints and risk, and provides a baseline or agreed plan against which actual and forecast performance can be discussed. PMBOK 8 emphasizes progressive elaboration and flexibility: even predictive projects may begin with milestones and refine detail through rolling wave planning, while adaptive work uses timeboxes, backlog ordering, velocity, and frequent replanning.
Understand the chapter
Schedule management turns the intended scope into a time-based model for delivery, communication, forecasting, and control. The schedule is not merely a date list: it links activities through logic, assigns durations and resources, exposes constraints and risk, and provides a baseline or agreed plan against which actual and forecast performance can be discussed. PMBOK 8 emphasizes progressive elaboration and flexibility: even predictive projects may begin with milestones and refine detail through rolling wave planning, while adaptive work uses timeboxes, backlog ordering, velocity, and frequent replanning.
Learning objectives
- Distinguish effort, duration, elapsed time, milestones, the schedule model, the project schedule, the schedule baseline, and a schedule forecast.
- Explain how activity definition, logical sequencing, estimating, and adjustment combine to produce a defensible schedule.
- Build and inspect a network using finish-to-start, start-to-start, finish-to-finish, and start-to-finish relationships, including justified leads and lags.
- Use critical-path, float, multipoint estimating, resource optimization, compression, and what-if analysis appropriately rather than mechanically.
- Select predictive, adaptive, or hybrid scheduling practices that fit the development approach and the uncertainty of the work.
- Interpret schedule variance, schedule performance index, burnup or burndown, velocity, trends, and forecasts without confusing indicators with causes.
- Maintain a realistic schedule through status updates, reserve reassessment, change control, backlog reprioritization, and stakeholder participation.
Key concepts
Dependency
A relationship through which one activity affects another’s timing.
Schedule baseline
An authorized timing model for comparison with performance.
Rolling-wave planning
Progressively adding detail to future work as knowledge improves.
Deeper understanding
Why it matters
A realistic forecast is more useful than an unchanged but obsolete baseline; preserve both for control.
Decision questions
- Which near-term dates are evidence-based, and which later dates still depend on assumptions?
- Can the team explain how each critical date follows from dependencies, estimates, and available resources?
- Are duration assumptions and changes visible, and did schedule acceleration introduce new risks?
Teach it back
- Distinguish effort, duration, elapsed time, milestones, the schedule model, the project schedule, the schedule baseline, and a schedule forecast.
- Explain how activity definition, logical sequencing, estimating, and adjustment combine to produce a defensible schedule.
- Build and inspect a network using finish-to-start, start-to-start, finish-to-finish, and start-to-finish relationships, including justified leads and lags.
Signals to notice
- A realistic forecast is more useful than an unchanged but obsolete baseline; preserve both for control.
- Adding people may lengthen an activity when coordination or indivisible work dominates.
- Progressive detail is compatible with predictive governance when future assumptions remain explicit.
Section-by-section reading
Use the printed page references to read each section in the official publication, then explain the idea in your own words.
Key concepts: realistic, progressive, communicative scheduling
The schedule communicates how and when scoped products, services, and results are expected, and supplies a basis for expectations and performance reporting. It also exposes potential delays while there is still time to respond. Detail should match the level of knowledge: even predictive projects may begin with milestones and elaborate activities progressively as information becomes available. The guide emphasizes revising the schedule as risks, external influences, and value-added work become clearer. Different levels of schedule granularity can coexist and may change with approach and organizational needs. A dated plan that cannot be kept realistic is not a reliable control device. What matters is whether the schedule model remains usable for decisions and stakeholder communication.
Understand this item
Why it matters: A credible schedule turns scope into a shared time model, exposes threats early, and supports forecasts and coordination instead of merely publishing target dates.
Decision to make: Commit detail only to the level supported by current knowledge, mark later assumptions, and update dates and granularity when risks, external conditions, or value-bearing work become clearer.
Do not confuse it with: A static dated list reports intentions; a useful schedule model explains timing, remains realistic, and changes when the evidence behind it changes.
Teach it back: Explain why a project can publish firm near-term activities and broader later milestones without abandoning schedule discipline.
Apply it: A plant upgrade starts with shutdown milestones, then details installation activities after vendor dimensions and permits are confirmed.
Check yourself: Which near-term dates are evidence-based, and which later dates still depend on assumptions?
Plan schedule management and develop the schedule model
Schedule management planning establishes how to develop, maintain, measure, and report the schedule. Its plan may specify accuracy, units, thresholds, release or iteration length, and links to organizational procedures. Developing the model analyzes activity sequences, durations, resources, and constraints to derive planned start and finish dates. It is iterative: estimates and reserves may need review before approving a baseline. The guide frames development as defining activities, determining sequence, estimating effort and duration, and adjusting the draft. Logical dependencies matter as much as dates because a late predecessor can move downstream work. A baseline is useful only when the assumptions, calendars, resource availability, and update rules behind it are understood.
Understand this item
Why it matters: Consistent update rules and a logic-based model make dates explainable, measurable, and controllable across dependencies, estimates, calendars, resources, and constraints.
Decision to make: Define scheduling precision, thresholds, reporting cadence, and iteration length, then test whether each critical date follows from sequenced work, realistic durations, resource availability, and reserves.
Do not confuse it with: The schedule management plan defines how scheduling will be done; the schedule model calculates and represents when work can occur from its underlying logic and constraints.
Teach it back: Build the reasoning for one milestone from predecessor logic, duration estimates, calendars, resources, and the rule used to approve its baseline.
Apply it: Sequence design approval before fabrication, reserve a testing window, and document the crew calendar before approving construction dates.
Check yourself: Can the team explain how each critical date follows from dependencies, estimates, and available resources?
Duration estimation, adjustment, and schedule control
Duration is not simply effort divided by headcount. The guide notes diminishing returns, coordination and learning costs from adding people, technology effects, decomposition level, and cognitive biases such as planning fallacy. Document the basis and assumptions for estimates so later changes can be interpreted. If the first schedule is unacceptable, adjust sequences, resources, or other components rather than silently asserting an implausible completion date. Monitoring and controlling schedule compares actual progress with the agreed schedule or baseline, updates forecasts, and manages changes. In iterative work, repeated learning and retrospectives can alter future plans. Compression or resource optimization has consequences for cost, quality, and risk and should be a conscious trade-off.
Understand this item
Why it matters: Transparent estimates and honest forecasts prevent optimistic dates from hiding coordination limits, uncertainty, and the cost, quality, or risk effects of acceleration.
Decision to make: Record the estimate basis and assumptions, diagnose variance, and if timing is unacceptable, deliberately adjust sequence, resources, scope, or reserves while assessing resulting trade-offs.
Do not confuse it with: Duration is elapsed time shaped by dependencies, capacity, learning, and constraints, not simply effort divided by the number of people assigned.
Teach it back: Explain why adding staff may not shorten a task and how the team should update the model and control decision when the original estimate fails.
Apply it: An extra electrician cannot halve a one-person certification inspection; revise the dependency and forecast instead of doubling staffing on paper.
Check yourself: Are duration assumptions and changes visible, and did schedule acceleration introduce new risks?
Tailoring by life cycle, deliverables, team, culture, and environment
The guide names life cycle and development approach, product or deliverable characteristics, team attributes, culture, project environment, and scheduling methods as tailoring factors. Stable physical deliverables may permit deeper upfront sequencing; changing product detail can favor progressive planning and iteration-based review. Team experience and availability affect how finely work can be estimated and coordinated. Organizational reporting expectations, external dependencies, and local working conditions affect calendars and update cadence. Select a scheduling approach that creates useful decisions, not merely a familiar chart. Tailoring does not remove the need to communicate reliable milestones and constraints; it decides how much detail to establish now, what to refine later, and which variances require action.
Understand this item
Why it matters: Scheduling detail and cadence must match what can actually be known and controlled, while still giving decision makers reliable milestones and visibility into constraints.
Decision to make: Select the planning horizon, decomposition level, tools, and update rhythm from deliverable stability, team experience, resource access, reporting culture, and external dependencies.
Do not confuse it with: Tailoring changes how and when detail is developed; it does not excuse vague commitments, ignored dependencies, or an unusable forecast.
Teach it back: Compare scheduling a fixed physical shutdown with scheduling an evolving digital release and identify what remains controlled in both.
Apply it: For a fixed rail closure, lock a detailed possession schedule; for an evolving passenger app, plan release milestones and refine upcoming iterations.
Check yourself: Does the planning horizon match what the team can know and control today?
Interactions with scope, resources, finance, risk, and stakeholders
A schedule is constrained by the work defined in scope, the people and equipment actually available, and financial limits on acquiring or accelerating them. Risk responses may require extra activities or reserve time; conversely, compressing work can create exposure or erode quality. Stakeholders depend on credible dates for coordination and expectations, while governance handles consequential baseline decisions. A changed deadline should therefore trigger an integrated review rather than a local edit to a chart. The domain's interactions are most visible where a predecessor cannot start because of a permit, resource conflict, or changed acceptance requirement. The schedule model should make those relationships intelligible to the decision makers.
Understand this item
Why it matters: Dates depend on agreed work, available capacity, funding, risk responses, and stakeholder commitments, so changing one milestone can propagate through the entire investment.
Decision to make: When a date moves or is compressed, trace the effect on downstream scope, resource bookings, spending, quality, risk exposure, public commitments, and governance approval.
Do not confuse it with: Editing a bar on a chart changes a displayed date; integrated schedule control changes the model only after considering the connected commitments and consequences.
Teach it back: Use a delayed permit to show how one dependency alters resources, cost, opening expectations, risk, and the sponsor's decision.
Apply it: A delayed permit moves excavation, equipment rental, and public opening; the sponsor evaluates a revised date against cost and safety.
Check yourself: Which other commitments move if this milestone slips or is compressed?
Check results: aligned phases, complete model, participation, and buffers
The guide's schedule checks are more specific than meeting a date. Align the scheduling approach with predictive, adaptive, or hybrid deliverables; represent the work from launch to close through phases with appropriate exit criteria; and inspect the plan for gaps or misalignment. Documentation should include relevant dependencies, durations, resource allocations, and milestones at a level appropriate to the approach. Check whether suitable tools and techniques were used and whether key stakeholders participated in building the schedule. Finally, test whether known constraints and risks have sufficient float, contingency, or alternate activity paths. A polished chart without credible dependencies, stakeholder input, or provision for known uncertainty does not meet these outcome checks.
Understand this item
Why it matters: A defensible schedule represents the whole delivery path, incorporates informed participants, and makes provision for known uncertainty rather than relying on a polished visual.
Decision to make: Verify phase and exit logic, dependencies, durations, allocations, milestones, stakeholder input, and suitable float, contingency, or alternate paths for material constraints and risks.
Do not confuse it with: Meeting a date is one result; schedule quality also depends on approach alignment, model completeness, credible participation, and resilience to known uncertainty.
Teach it back: Show how a reviewer could find the next threatened milestone, its causal dependency, available buffer, response owner, and required decision.
Apply it: At each review, show the current completion forecast, the permit dependency, mitigation owner, and approved change to opening date.
Check yourself: Can a stakeholder identify the next threatened milestone and the decision needed to protect it?
Apply it to a project
Hospital electronic-record deployment A hospital must deploy a new electronic-record system in 20 weeks. Software configuration can iterate, but regulatory validation and cutover have fixed approvals. Two integration engineers are shared with another program. Plan Schedule Management sets weekly status, a two-week software cadence, day-based calendars, a five-day variance threshold, and formal control for the regulatory and cutover baseline. Develop Schedule decomposes the near-term release, links data migration, interface testing, training, validation, and cutover, and keeps later configuration work at rolling-wave detail. The network shows validation-to-cutover as critical. Resource leveling reveals the shared engineers would delay interface testing by eight days; negotiation secures one engineer earlier and resequences noncritical training preparation. Three-point estimates and simulation are used for data cleansing. A management review selects a staged migration rehearsal rather than optimistic single-point dates. During execution, accepted features and burnup are reviewed every sprint, while the predictive milestone network is statused weekly. A forecasted validation delay triggers a risk response and change analysis without silently moving the baseline. A hybrid schedule can preserve hard external commitments while using empirical replanning for uncertain product work; resource and risk analysis make the integrated plan credible.
What to watch for
- Misconception: The Gantt chart is the schedule. Correction: A Gantt chart is a view. The schedule model also includes logic, calendars, constraints, resources, estimates, assumptions, and data required to calculate and update dates.
- Misconception: Effort and duration are interchangeable. Correction: Effort is labor required; duration is elapsed work periods under assigned resources and calendars. Doubling staff rarely halves duration because work may be indivisible and coordination grows.
- Misconception: Every predictive detail must be fixed before execution. Correction: PMBOK 8 supports progressive elaboration and rolling wave planning even in predictive settings when information is incomplete.
- Misconception: A zero-float path will remain critical. Correction: Status, logic, durations, constraints, and resources can change the critical and near-critical paths; recalculate after meaningful updates.
- Misconception: Updating a forecast means changing the baseline. Correction: Actuals and forecasts are updated routinely. A predictive baseline changes only through the authorized change process.
- Misconception: Schedule compression is free acceleration. Correction: Fast tracking raises coordination and rework risk; crashing usually adds cost or scarce resources. Both require integrated evaluation.
Test your reasoning
Which process creates the schedule baseline and project schedule?
Show answer and reasoning
Develop Schedule Plan Schedule Management defines how scheduling will be done; Develop Schedule applies sequencing, estimates, resources, and constraints to produce the model, schedule, and baseline.
An activity has ES Day 4, duration 5, and LS Day 7 using inclusive day numbering. What are EF and total float?
Show answer and reasoning
EF 8; float 3 EF = 4 + 5 - 1 = 8. Total float = LS - ES = 7 - 4 = 3 days.
Why is adding twice as many people not assumed to halve an activity's duration?
Show answer and reasoning
Coordination, learning, indivisible work, and diminishing returns can offset added capacity PMBOK 8 explicitly warns about diminishing returns, knowledge transfer, learning curves, and coordination. Resource changes should be modeled, not treated as linear.
A status update predicts a later finish but no scope or approved plan change has occurred. What should happen first?
Show answer and reasoning
Update actuals and the forecast, analyze causes and responses, and raise a change request if needed Forecasts should reflect current reality. Predictive baselines remain controlled and are changed only through authorization.
What does SPI = 0.90 mean?
Show answer and reasoning
Earned value is 90% of planned value at the data date SPI = EV/PV. It is a value-based efficiency indicator, not a direct conversion to calendar delay, cost variance, or float.
Study companion only; the official guide is available from PMI.