PMI-SP PMI Scheduling Professional Exam Topics and Questions

Schedule Strategy sets the foundation for everything that follows. It's where you define how scheduling will work across the project lifecycle: what gets controlled, who approves changes, how baselines are managed, and which standards apply. The cost comes in the form of incomplete or inconsistent policy. If your configuration management procedures are vague or your schedule management plan leaves room for interpretation, you'll spend the rest of the project fighting ambiguity.

– Configuration management and baseline control

Task 1 addresses the mechanics of schedule control: how you store, retrieve, and maintain schedule files, and how you enforce change control once a baseline is set. This means defining who has access, what formats are authoritative, and how versions are tracked. The exam expects you to know that configuration management is not just filing; it's the system that prevents unauthorized changes and ensures everyone works from the same baseline. Best practices, organizational policies, and governing standards all feed into these procedures. You need to articulate how accessibility and storage work in a controlled environment, and how baseline control protects the integrity of the schedule over time.

– Schedule approach, methodology, and operational procedures

Tasks 2, 3, and 5 cover how you tailor the scheduling approach to the project's unique characteristics, then codify that approach in the schedule management plan. Task 2 focuses on defining schedule requirements based on enterprise environmental factors and organizational process assets. Task 3 goes deeper: you select the scheduling tool, set activity granularity, choose analysis techniques, establish performance thresholds, decide on presentation formats, and determine EVM implementation. Task 5 ensures the project team understands their role in the process. The exam tests whether you can distinguish between a schedule approach (the high-level strategy) and the detailed operational procedures that make it enforceable. You also need to recognize that scheduling policies are not static; they reflect the project's context and the organization's maturity.

– Integration with the broader project management plan

Task 4 requires you to weave scheduling into every other knowledge area: integration, scope, cost, quality, resources, communication, risk, and procurement. This is not a box-ticking exercise. The exam wants to see that you understand how schedule constraints affect procurement timelines, how risk events alter schedule buffers, and how resource plans shape activity durations. Contract requirements often impose specific scheduling obligations, and those obligations must be reflected in the relevant subsidiary plans. The integration work happens early, and if you skip it, you discover the gaps when it's too late to adjust without a baseline change.

How Schedule Strategy is tested

At 14 percent, this topic sets the tone for the rest of the exam. Items here test whether you can distinguish between a schedule management plan and a schedule model, and whether you understand that configuration management is an active control system rather than a passive archive. You'll face scenarios where a project team is unclear on approval authority, or where baseline control has broken down, and you'll need to identify the root cause in the strategy layer. Questions often present a situation where multiple standards or policies apply, and you must select the one that governs. Candidates lose marks by choosing the technically correct scheduling technique when the real issue is a missing or incomplete policy. The exam also tests whether you recognize that the schedule approach must be defined before detailed planning begins, and that skipping this step leads to rework later. Another common trap is conflating the schedule management plan with the communications plan; the former defines how scheduling is done, the latter defines how schedule information is shared.

Schedule Planning and Development is where strategy becomes a working model. At 31 percent, this is the heaviest topic on the exam, and that weight reflects the sheer number of decisions you make between initial scope decomposition and baseline approval. The cost is in the sequencing and resource logic. Get the dependencies wrong, miss a constraint, or underestimate durations, and the schedule becomes a fiction that no one trusts.

– Decomposition and work definition

Tasks 1 and 2 cover how you break down scope into schedulable units. The WBS, OBS, control accounts, and work packages are the structural elements that connect scope to schedule. Task 1 emphasizes communication with subject matter experts and analysis of contractual commitments; you're not inventing the breakdown, you're discovering it. Task 2 takes the work packages and decomposes them further into activities and milestones. The exam expects you to know that activities represent work, milestones represent decision points or deliverables, and that decomposition stops when you reach a level that can be estimated, assigned, and monitored. Scheduling policies and procedures from Topic 1 guide how granular you go. The trap is decomposing too far or stopping too early, either of which makes the schedule unmanageable.

– Duration estimation and sequencing logic

Tasks 3 and 4 build the schedule's time dimension. Task 3 is about estimating activity durations using techniques like three-point, parametric, analogous, or PERT. Each technique has a use case: three-point when uncertainty is high, parametric when you have historical data, analogous when the work resembles past projects. The exam tests whether you can match the technique to the situation. Task 4 is sequencing: you define dependencies (finish-to-start, start-to-start, and so on), incorporate milestones, and apply constraints like calendars, geography, and contractual deadlines. The schedule model is dynamic because dependencies propagate change; move one activity and the downstream path shifts. Candidates lose marks by treating constraints as preferences or by ignoring external dependencies that cross program boundaries.

– Path analysis and resource assignment

Tasks 5, 6, and 7 turn a logical schedule into a resource-constrained one. Task 5 identifies the critical path and near-critical paths using CPM, Critical Chain, PERT, or Monte Carlo simulation. The critical path determines the shortest possible project duration; near-critical paths are the ones that could become critical if anything slips. Task 6 develops the resource breakdown structure, determines who is available when, and assigns resources to activities. Task 7 adjusts the model based on resource availability and budget. The exam tests whether you understand that the critical path can shift when resources are constrained, and that a schedule is not realistic until resource and budget limits are applied. The trap is presenting a resource-loaded schedule as if it were resource-constrained, or assuming unlimited availability.

– Alignment, risk analysis, and baseline approval

Tasks 8 through 12 finalize the schedule and prepare it for baseline approval. Task 8 aligns the project schedule with the program plan or integrated master plan, ensuring that enterprise objectives and contract documentation are reflected. Task 9 checks major milestones against the SOW, contract, or memorandum of understanding to confirm delivery estimates meet required deadlines. Task 10 performs schedule risk analysis using quantitative tools to determine if milestone dates are achievable within acceptable risk tolerances. Task 11 obtains consensus from the customer, sponsor, project manager, and project team to establish the approved baseline. Task 12 establishes the Performance Measurement Baseline, enabling EVM. The exam expects you to recognize that baseline approval is not a formality; it's a commitment. Risk analysis must happen before approval, and consensus means all parties understand what they are agreeing to. Candidates often rush to baseline without validating achievability or obtaining genuine stakeholder buy-in.

How Schedule Planning and Development is tested

With 31 percent of the exam, this topic generates the most items. Questions test whether you can select the correct estimation technique given the available data, whether you can identify missing or incorrect dependencies, and whether you understand the difference between a resource-loaded and a resource-constrained schedule. You'll see scenarios where a critical path calculation is wrong because a constraint was ignored, or where a schedule is baselined before risk analysis is complete. The exam also tests your ability to distinguish between internal, external, and cross-program dependencies, and to recognize when a milestone is contractually imposed versus discretionary. Another common trap is treating the Performance Measurement Baseline as identical to the schedule baseline; PMB includes cost and scope integration. Candidates lose marks by choosing the most sophisticated technique when a simpler one is appropriate, or by failing to recognize that consensus requires active stakeholder engagement, not just a signature. The weight of this topic means you cannot afford weak coverage in any of the task areas.

Schedule Monitoring and Controlling is the heaviest topic at 35 percent, and that tells you where the exam focus lies. This is not passive reporting. You're collecting status, auditing schedule logic, analyzing alternatives, incorporating approved changes, and maintaining baseline integrity, all while the project is moving. The cost is in the lag between when something goes wrong and when you detect it. Miss a status update cycle, skip an audit, or fail to recognize a critical path shift, and you're managing to outdated information.

– Status collection and resource tracking

Tasks 1 and 2 establish the data inputs for schedule control. Task 1 is about collecting activity status at defined intervals from activity owners using reports, meetings, inspections, or other standard procedures. The exam expects you to know that status collection is not ad hoc; it follows the intervals and procedures defined in the schedule management plan. Task 2 collects resource information and updates via timesheets, reports, or meetings to report on resource utilization and availability. The distinction matters: activity status tells you what work is complete, resource information tells you whether the people and equipment are being used as planned and whether they remain available. Candidates often conflate the two. The exam tests whether you understand that status collection is the foundation of all schedule control, and that inconsistent or late status updates compromise every downstream analysis.

– Schedule analysis, audit, and optimization

Tasks 3 and 4 turn status into insight. Task 3 is schedule analysis and audit, performed on both in-house and subcontractor schedules using industry standards, guidelines, and best practices. This is where you identify schedule status, changes, impacts, or issues. The audit checks whether the schedule model still reflects the project logic, whether dependencies are intact, whether the critical path is correctly calculated, and whether subcontractor schedules integrate properly. Task 4 identifies alternative execution options using what-if scenario analysis to optimize the schedule. The exam expects you to recognize that optimization is not about padding; it's about finding a path that meets the deadline with acceptable risk. Scenario analysis lets you test options before committing to one. Candidates lose marks by confusing audit (checking the model's integrity) with analysis (interpreting status against the baseline), or by proposing alternatives without running the scenarios first.

– Change control and baseline maintenance

Tasks 5 and 6 manage how approved changes are incorporated and how the baseline is maintained. Task 5 incorporates approved risk mitigation activities into the schedule using defined change control processes, establishing a new Performance Measurement Baseline. Task 6 updates the schedule model and documents baseline changes received through formal change control, maintaining an accurate schedule and facilitating forensic analysis if required. The exam tests whether you understand that no change enters the schedule without passing through formal change control, and that every baseline change must be documented with enough detail to support later forensic analysis. The trap is updating the schedule model without updating the baseline, or vice versa. Another trap is treating risk mitigation activities as if they don't require change control. The PMB is a control point; changing it is a significant event, and the exam expects you to treat it as such.

How Schedule Monitoring and Controlling is tested

At 35 percent, this topic dominates the exam. Items test whether you can identify when status collection intervals are inadequate, whether you recognize a schedule model that has drifted from the baseline, and whether you can distinguish between a schedule update and a baseline change. You'll see scenarios where a subcontractor schedule is not integrated, where a critical path shift goes undetected, or where a change is implemented without formal approval. The exam also tests your understanding of what-if analysis: you need to know when to run scenarios, what variables to test, and how to interpret the results. Another common area is the Performance Measurement Baseline. Questions will present a situation where risk mitigation activities are added to the schedule, and you must determine whether a new PMB is required. Candidates lose marks by choosing to update the schedule model when the correct action is to initiate change control, or by assuming that all schedule changes require a new baseline. The exam expects you to know the difference between routine updates (which do not change the baseline) and approved changes (which do). The weight of this topic means you cannot afford to be weak on change control procedures or on the mechanics of schedule audits.

Schedule Closeout accounts for 6 percent of the exam, but its weight understates its importance. Closeout is where you formalize acceptance, evaluate performance, capture lessons learned, and archive everything in a way that satisfies contractual requirements and supports future forensic analysis. The cost is in the incompleteness. If you skip the performance evaluation, fail to update organizational process assets, or archive files in a way that makes retrieval difficult, you lose the value of everything you learned during execution.

How Schedule Closeout is tested

At 6 percent, this topic generates fewer items, but they test whether you understand that closeout is a formal process with specific deliverables. Questions present scenarios where final acceptance is delayed because a contractual schedule component is missing, or where lessons learned are not documented in a way that updates organizational process assets. The exam expects you to know that final schedule reports include EVM calculations and variance analysis, and that these reports are distributed to stakeholders as part of closeout. You'll also see questions on archiving: what files must be retained, how they should be stored, and why forensic schedule analysis requires a complete and retrievable archive. Candidates lose marks by treating closeout as administrative rather than analytical, or by assuming that final acceptance happens automatically when the last activity is complete. The exam also tests whether you recognize that evaluating schedule performance means comparing actual results against the baseline schedule, the scheduling approach, and the implementation, not just against the final deadline. Another trap is failing to solicit stakeholder feedback as part of the lessons-learned process. The low weight means you can't afford to ignore this topic, because every mark counts, and closeout questions are often straightforward if you know the required steps.

Stakeholder Communications Management closes the exam at 14 percent. This topic is not about reporting for its own sake; it's about maintaining stakeholder support and elevating awareness of issues that could derail the schedule. The cost is in the mismatch between what you communicate and what stakeholders need to hear. If your status updates are too detailed for senior management or too vague for the project team, or if you fail to communicate a schedule issue before it becomes a crisis, you lose credibility and support.

How Stakeholder Communications Management is tested

At 14 percent, this topic tests whether you understand that communication is governed by the communication management plan, and that all schedule-related communication must be consistent with that plan. Questions present scenarios where stakeholder support is eroding because visibility of the schedule is inadequate, or where a schedule issue is communicated too late or to the wrong audience. The exam expects you to know that developing and fostering relationships is an ongoing activity, not a one-time event, and that maintaining visibility means working with the project manager and stakeholders to ensure the schedule is understood and trusted. You'll also see questions on the content and format of status updates: verbal and written updates must include the impact of corrective actions, not just current status. Another common area is escalation: when a schedule issue could impact delivery of project scope or adherence to the schedule management plan, you must elevate awareness to relevant stakeholders. Candidates lose marks by choosing to continue routine reporting when escalation is required, or by escalating issues that should be handled at the project level. The exam also tests whether you recognize that communication is a two-way process; fostering relationships means listening to stakeholder concerns and adjusting your communication approach accordingly. The trap is treating communication as a broadcast activity rather than a relationship-building one.