PMI-SP — PMI Scheduling Professional Exam Blueprint

How to Use This Exam Blueprint

Use this independent Exam Blueprint to organize final review for the PMI Scheduling Professional (PMI-SP) exam from PMI. It is a practical study map, not an official scoring outline. Because official weights can change, the sections below are framed as readiness areas rather than weighted domains.

For each area, mark your status:

• Ready: you can apply the concept in a scenario without looking it up.
• Review: you understand the concept but miss details, sequencing, or decision logic.
• Weak: you recognize the term but cannot confidently choose the next action.
• Practice: you need more scenario questions, calculations, or artifact interpretation.

PMI-SP readiness areas at a glance

Schedule strategy and governance checklist

Core readiness checks

• I can explain the purpose of a schedule management approach before detailed schedule development begins.
• I can identify schedule inputs from the charter, business case, scope baseline, delivery approach, contract terms, and stakeholder expectations.
• I can distinguish the schedule model, schedule baseline, schedule reports, and schedule management plan.
• I can define how schedule progress will be measured, collected, validated, and reported.
• I can identify who approves the schedule baseline and who authorizes changes.
• I can recognize when tailoring is needed for predictive, agile, hybrid, phased, outsourced, or highly regulated work.
• I can connect schedule strategy to benefits, value delivery, operational deadlines, compliance dates, and market windows.
• I can identify schedule governance items such as thresholds, escalation rules, control points, reporting frequency, and review forums.
• I can determine when a high-level roadmap is enough and when a detailed integrated schedule model is needed.
• I can evaluate whether the schedule strategy is realistic given known constraints, assumptions, risks, and resource availability.

Strategy artifacts to know

Schedule planning and development checklist

Activity definition and decomposition

• I can turn approved scope into schedule activities without confusing deliverables with activities.
• I can identify when work is not decomposed enough to estimate, sequence, or control.
• I can distinguish activities, work packages, planning packages, milestones, and summary tasks.
• I can recognize missing activities such as reviews, approvals, procurement lead time, testing, rework, transition, training, and closeout.
• I can identify rolling-wave planning situations where near-term work is detailed and future work remains higher level.
• I can spot schedules that hide risk by using overly large activities or vague task names.

Sequencing and logic

• I can identify finish-to-start, start-to-start, finish-to-finish, and start-to-finish relationships.
• I can explain mandatory, discretionary, internal, and external dependencies.
• I can recognize when a lead or lag is used appropriately and when it masks poor logic.
• I can evaluate whether schedule logic reflects real work flow rather than a desired finish date.
• I can identify open starts, open finishes, excessive constraints, dangling logic, and missing successors.
• I can recognize when a milestone should be tied to logical predecessors rather than placed by date only.
• I can evaluate whether external dependencies require monitoring, contracts, agreements, or escalation.

Duration and resource estimating

• I can distinguish effort, duration, and elapsed time.
• I can identify when resource calendars, holidays, shifts, location, productivity, and availability affect duration.
• I can use analogous, parametric, expert judgment, bottom-up, and three-point estimating concepts in scenarios.
• I can recognize when estimates need assumptions, basis of estimate, confidence ranges, or risk information.
• I can identify when resource constraints require leveling, smoothing, re-sequencing, or scope negotiation.
• I can distinguish schedule compression from estimate manipulation.
• I can evaluate whether estimates are realistic given uncertainty and historical performance.

Baseline development

• I can explain what should be true before a schedule baseline is approved.
• I can identify whether the schedule is integrated with scope, resources, cost, risk, procurement, and quality plans.
• I can recognize when stakeholder agreement is needed before committing to milestone dates.
• I can distinguish the current working schedule from the approved schedule baseline.
• I can identify when a target date, imposed date, or contractual date should be represented transparently.
• I can identify schedule quality issues before baseline approval.

Schedule analysis and calculation checks

Critical path and float

You should be comfortable interpreting schedule networks and answering “what happens if this activity slips?” questions.

• I can identify the critical path as the path controlling the project finish in the current schedule model.
• I can calculate or interpret total float.
• I can calculate or interpret free float.
• I can explain why an activity with float can still be important.
• I can identify near-critical paths and explain why they require monitoring.
• I can interpret negative float as a warning that the current plan does not meet a required date.
• I can explain how constraints, calendars, and resource leveling may change critical path results.
• I can avoid assuming the longest list of tasks is automatically the critical path without analyzing dates and logic.

Key formulas to know conceptually:

\[ \text{Total Float} = \text{Late Start} - \text{Early Start} \]\[ \text{Total Float} = \text{Late Finish} - \text{Early Finish} \]\[ \text{Free Float} = \text{Earliest Start of Successor} - \text{Early Finish of Current Activity} \]

Estimating and uncertainty

• I can interpret optimistic, most likely, and pessimistic estimates.
• I can identify when three-point estimating is useful because uncertainty is meaningful.
• I can distinguish a deterministic schedule from a probabilistic schedule analysis.
• I can explain the purpose of schedule risk analysis without treating it as a guarantee.
• I can recognize when contingency, management reserve, or risk response planning may affect schedule expectations.

Common three-point estimate formula:

\[ \text{Expected Duration} = \frac{\text{Optimistic} + 4(\text{Most Likely}) + \text{Pessimistic}}{6} \]

Earned value schedule indicators

If a scenario uses earned value information, be ready to interpret schedule-related indicators without over-relying on a single metric.

\[ \text{Schedule Variance} = \text{Earned Value} - \text{Planned Value} \]\[ \text{Schedule Performance Index} = \frac{\text{Earned Value}}{\text{Planned Value}} \]

Readiness checks:

• I can interpret positive, zero, and negative schedule variance.
• I can interpret SPI above, equal to, or below 1.0.
• I can explain why earned value indicators may need to be combined with critical path analysis.
• I can recognize that being “ahead” by earned value does not always mean the critical milestone is safe.
• I can use schedule performance data to support forecasting, not to replace professional judgment.

Schedule monitoring and controlling checklist

Status collection and schedule updates

• I can identify what status data is needed: actual start, actual finish, remaining duration, percent complete, physical progress, and forecast finish.
• I can explain the purpose of the data date.
• I can determine whether status information is credible, complete, and timely.
• I can identify when reported percent complete conflicts with remaining duration or actual work accomplished.
• I can update the schedule model without overwriting baseline history.
• I can distinguish progress reporting from schedule forecasting.
• I can recognize when a schedule update creates logic, constraint, or sequencing problems.
• I can identify when missed updates require follow-up with activity owners.

Variance analysis and forecasting

• I can compare current forecast dates against the approved baseline.
• I can determine whether a variance is within agreed thresholds or needs escalation.
• I can identify root causes of schedule variance, not just symptoms.
• I can distinguish one-time delay from trend-based deterioration.
• I can assess the impact of delays on critical path, near-critical paths, milestones, handoffs, and external commitments.
• I can recommend corrective action, preventive action, defect repair, or change request based on scenario facts.
• I can evaluate schedule recovery options for feasibility, risk, cost, and stakeholder impact.

Change control and baseline management

• I can determine when a schedule change requires formal change control.
• I can distinguish approved baseline change from routine forecast update.
• I can identify schedule impacts caused by scope changes, risk events, resource changes, quality failures, or procurement delays.
• I can explain why baseline changes should be documented and approved, not silently absorbed.
• I can identify which artifacts may need updates after an approved schedule change.
• I can recognize when a requested finish date is a constraint to analyze, not an automatic baseline change.
• I can avoid choosing shortcuts that bypass governance because of pressure.

Schedule compression and recovery checklist

Recovery decision prompts

Ask these questions before choosing an answer in a schedule recovery scenario:

• Is the delayed activity on the critical path or a near-critical path?
• Does the delay affect a contractual, regulatory, operational, or value-delivery milestone?
• Is the cause scope change, poor estimating, resource shortage, quality defect, vendor delay, risk event, or unclear ownership?
• Is there float available before the next key milestone?
• Does the proposed recovery action increase cost, risk, or quality exposure?
• Is approval required before changing the baseline?
• Who needs to be informed before the plan changes?
• What artifact must be updated after the decision?

Stakeholder communication checklist

Reporting readiness

• I can tailor schedule reports for executives, sponsors, project teams, customers, vendors, and governance boards.
• I can distinguish detail needed for control from summary needed for decision-making.
• I can explain milestone charts, lookahead schedules, variance reports, trend reports, and critical path summaries.
• I can communicate schedule risk without hiding uncertainty.
• I can present alternatives with schedule, cost, risk, and value tradeoffs.
• I can escalate issues according to thresholds and governance rules.
• I can facilitate schedule review meetings focused on decisions, assumptions, dependencies, and action owners.
• I can avoid reporting only favorable information when the forecast has deteriorated.

Communication decision table

Predictive, agile, and hybrid scheduling readiness

The PMI-SP exam identity is scheduling-focused, so be prepared to reason across delivery approaches when scenarios involve different planning horizons or levels of uncertainty.

Artifact checklist: what to know and when to update it

Scenario and decision-point checklist

“What should the scheduler do next?” prompts

Tailoring prompts

• Is the schedule detail appropriate for the project size, complexity, uncertainty, and governance needs?
• Are stakeholders receiving the right level of information at the right time?
• Does the schedule model support decision-making, or is it only a documentation exercise?
• Are agile or rolling-wave components represented with suitable planning horizons?
• Are external dependencies visible and actively managed?
• Are control thresholds practical enough to trigger timely action?

Common weak areas and traps

High-value “Can you do this?” checklist

Before exam day, you should be able to answer yes to most of these without notes.

Planning and model-building

• Can you identify missing activities from a scope description?
• Can you choose the correct dependency type from a work-flow scenario?
• Can you explain the difference between lead, lag, dependency, and constraint?
• Can you identify when a milestone is unsupported by logic?
• Can you determine whether a schedule is ready for baseline approval?
• Can you spot unrealistic durations caused by ignored calendars or resource limits?
• Can you decide whether rolling-wave planning is appropriate?

Analysis and control

• Can you identify the critical path from a simple network?
• Can you determine the effect of a delay on the project finish date?
• Can you explain total float and free float in plain language?
• Can you interpret negative float and recommend next steps?
• Can you choose between crashing, fast tracking, leveling, smoothing, and re-sequencing?
• Can you decide when a schedule issue requires escalation?
• Can you distinguish corrective action from a formal baseline change?

Communication and judgment

• Can you tailor schedule communication for executive, technical, vendor, and customer audiences?
• Can you explain schedule risk without overstating certainty?
• Can you recommend a decision when schedule, cost, quality, and scope conflict?
• Can you identify the artifact to update after a schedule-impacting event?
• Can you choose the ethical response when asked to hide or soften a schedule problem?
• Can you identify when to validate information before reporting it?

Final-week PMI-SP review checklist

Five to seven days before the exam

• Review schedule strategy, planning, monitoring, communication, and closeout as connected work, not isolated definitions.
• Practice critical path, float, and schedule variance interpretation.
• Review schedule compression and resource optimization decisions.
• Revisit artifact update rules: schedule model, baseline, risk register, issue log, change log, reports, and lessons learned.
• Work scenario questions that ask “what should the scheduler do next?”
• Create a short list of formulas, definitions, and decision rules you still confuse.

Two to four days before the exam

• Drill weak areas rather than rereading broad material.
• Practice explaining why wrong answers are wrong.
• Review scenarios involving negative float, missed milestones, unapproved scope, vendor delays, and stakeholder pressure.
• Review professional conduct: accurate reporting, transparency, confidentiality, and realistic forecasting.
• Confirm you can separate routine schedule updates from formal baseline changes.

Day before the exam

• Do a light review of formulas and artifact relationships.
• Recheck common traps: constraints, lags, percent complete, near-critical paths, and unsupported milestones.
• Avoid learning large new topics late; focus on confidence and decision patterns.
• Rest enough to read long scheduling scenarios carefully.

Practical next step

Use this checklist to select your next practice set: choose one weak readiness area, answer a focused block of PMI-SP-style scheduling questions, then review every missed item by asking:

1. What schedule concept was being tested?
2. What artifact or decision point mattered?
3. What would a professional scheduler do next?
4. What clue in the scenario made the best answer better than the others?