PMI-SP — PMI Scheduling Professional Quick Review

How to Use This Quick Review

This Quick Review is for candidates preparing for the PMI Scheduling Professional (PMI-SP) exam, code PMI-SP, from PMI. It is PM Mastery review support designed to help you quickly refresh high-yield scheduling concepts before moving into topic drills, mock exams, and detailed explanations.

Use this page to check whether you can:

• Build and evaluate a credible schedule model.
• Distinguish planning, baseline approval, status updating, forecasting, and change control.
• Apply critical path, float, resource, risk, and performance concepts in scenario questions.
• Avoid common exam traps such as “just update the baseline,” “add resources to everything,” or “treat percent complete as objective progress.”

Exam mindset: answer as a scheduling professional who protects schedule integrity, uses documented methods, communicates uncertainty clearly, and supports project decision-making with reliable schedule information.

High-Yield Review Map

Core Scheduling Lifecycle

A strong PMI-SP exam answer usually follows this logic:

1. Define the scheduling approach

   • Confirm scope basis, scheduling method, tool conventions, calendars, coding structure, and reporting needs.
   • Establish update frequency, roles, approvals, and change control expectations.

2. Develop the schedule model

   • Decompose work, define activities, sequence logically, estimate durations, assign resources, apply calendars, and document assumptions.

3. Analyze and validate

   • Run critical path analysis, check float, review resource feasibility, test constraints, perform risk analysis, and correct schedule quality problems.

4. Approve the baseline

   • Obtain stakeholder acceptance of the schedule baseline as the agreed performance reference.

5. Monitor and control

   • Collect status, update actuals and remaining work, compare to baseline, forecast outcomes, recommend corrective action, and manage approved changes.

6. Close and learn

   • Preserve as-built data, document variances, capture lessons learned, and improve future scheduling practices.

Key Artifact Distinctions

Schedule Strategy and Governance

What a Good Schedule Management Approach Defines

A schedule management approach should clarify:

• Scheduling methodology and tool conventions.
• Required level of detail.
• Activity coding and naming standards.
• Calendar rules and time units.
• Estimating approach.
• Resource planning expectations.
• Update frequency and data date discipline.
• Baseline approval process.
• Change control process.
• Reporting formats by stakeholder group.
• Schedule quality review expectations.
• Roles and responsibilities for status collection, approval, and analysis.

Common Strategy Mistakes

Level of Detail Decision Rule

Use enough detail to control the work, not so much that the schedule becomes unmaintainable.

Good activity detail usually supports:

• Clear responsibility.
• Measurable start and finish.
• Reasonable duration for the control cycle.
• Logical connection to predecessors and successors.
• Meaningful progress reporting.

If an activity is too broad, progress becomes subjective. If it is too granular, the schedule becomes administrative noise.

Developing the Schedule Model

From Scope to Activities

A credible schedule begins with scope clarity.

Common trap: a milestone is not work. If a question describes a milestone with effort, duration, or resources, the exam may be testing whether you recognize that the work activities leading to the milestone need to be defined.

Dependencies and Relationships

Most scheduling questions use precedence logic. Know the relationship types.

Dependency Types

Leads and Lags

• A lag delays the successor after the dependency condition is met.
• A lead allows the successor to start before the predecessor is fully complete.

Use leads and lags carefully. A schedule with excessive lags or leads may be harder to validate because hidden work or waiting time is embedded in relationships instead of shown as explicit activities.

Better exam answer when possible: make significant waiting, curing, review, approval, or handoff periods visible as activities rather than burying them in unexplained lag.

Estimating Durations

Duration, Effort, and Elapsed Time

A basic relationship is:

\[ \text{Duration} = \frac{\text{Work}}{\text{Resource Units}} \]

This relationship is simplified. Real schedules must also account for calendars, learning curves, handoffs, availability, productivity, and constraints.

Estimating Methods

For three-point estimates using a beta/PERT-style weighted average:

\[ E = \frac{O + 4M + P}{6} \]\[ \sigma = \frac{P - O}{6} \]

Where:

• \(O\) = optimistic estimate
• \(M\) = most likely estimate
• \(P\) = pessimistic estimate
• \(E\) = expected duration
• \(\sigma\) = standard deviation estimate

Exam trap: three-point estimating is not a substitute for risk management. It helps represent uncertainty, but schedule risk still requires analysis, response planning, and monitoring.

Critical Path and Float

Critical Path Basics

The critical path is the path through the schedule that determines the earliest possible project finish, based on current logic, durations, calendars, constraints, and status.

Important points:

• A project can have multiple critical paths.
• Near-critical paths can become critical after small delays.
• Critical path can change after status updates, resource leveling, or approved changes.
• Negative float can appear when a required date is earlier than the calculated completion date.
• Critical does not mean “most important” or “highest risk”; it means schedule-driving under the current model.

Forward and Backward Pass

Forward pass calculates early dates:

\[ \mathrm{EF} = \mathrm{ES} + \mathrm{Duration} \]\[ \mathrm{ES}_{\text{successor}} = \max(\mathrm{EF}_{\text{predecessors}}) \]

Backward pass calculates late dates:

\[ \mathrm{LS} = \mathrm{LF} - \mathrm{Duration} \]\[ \mathrm{LF}_{\text{predecessor}} = \min(\mathrm{LS}_{\text{successors}}) \]

Float:

\[ \mathrm{Total\ Float} = \mathrm{LS} - \mathrm{ES} \]\[ \mathrm{Total\ Float} = \mathrm{LF} - \mathrm{EF} \]\[ \mathrm{Free\ Float} = \min(\mathrm{ES}_{\text{successors}}) - \mathrm{EF} \]

The exam usually tests the concept more than date-counting quirks. Watch for inclusive versus exclusive date conventions if a calculation question gives calendar dates.

Types of Float

What Can Change the Critical Path?

Schedule Quality Checks

A schedule must be technically credible before its outputs can be trusted.

A strong answer often starts with validating the schedule model before relying on its forecast.

Resources, Calendars, and Optimization

Resource Planning

Resource planning connects activity estimates to real execution capacity.

Key concepts:

• Resource availability affects duration and sequence.
• Specialized resources can create bottlenecks.
• Calendars affect working time and forecast dates.
• Productivity assumptions must be realistic.
• Shared resources across projects can create external schedule risk.

Leveling vs. Smoothing

Candidate trap: if resources are overallocated, the right first step is not automatically to demand more people. Analyze the constraint, priorities, float, critical path impact, and feasible optimization options.

Compression Techniques

Decision rule: compression should usually focus on critical or near-critical paths. Shortening a noncritical activity may consume money without improving the finish date.

Constraints, Assumptions, and Calendars

Constraints

Constraints should be used deliberately and documented.

Constraints are sometimes legitimate, especially for externally imposed milestones or business commitments. The exam trap is treating constraints as a substitute for schedule logic.

Assumptions

Document assumptions about:

• Resource availability.
• Productivity.
• Review and approval durations.
• External dependencies.
• Procurement or vendor lead times.
• Access windows.
• Calendars and nonworking periods.
• Technical complexity.
• Risk response effectiveness.

When assumptions change, assess schedule impact rather than silently editing dates.

Schedule Risk and Uncertainty

Schedule Risk Concepts

A deterministic CPM schedule gives one forecast based on selected assumptions. Real projects have uncertainty. Schedule risk analysis asks, “How likely is this finish date given uncertainty in durations, logic, resources, and risks?”

High-yield concepts:

• Uncertainty should be visible and analyzed.
• Critical path can shift under risk simulation.
• Near-critical paths matter.
• Contingency reserves should be based on analysis, not hidden padding.
• Risk responses must be integrated into the schedule.
• Schedule risk should be communicated in probability or range terms when appropriate.

Common Schedule Risk Sources

Reserves and Padding

Candidate trap: padding individual activities can reduce transparency and make the schedule harder to manage. Explicit reserves or buffers, with governance, are more defensible.

Monitoring and Controlling the Schedule

Data Date Discipline

The data date is the status date through which progress is reported. Reliable updates require consistency:

• Actual starts and finishes should be accurate.
• Remaining duration should reflect current forecast, not original duration minus time elapsed.
• No actual work should be recorded after the data date.
• In-progress activities should have realistic remaining work.
• Out-of-sequence progress should be investigated.
• Forecast dates should be recalculated after status is entered.

Candidate trap: percent complete alone is often subjective. A schedule professional should look for objective progress measures and remaining duration.

Progress Measurement Methods

Variance and Forecasting

High-yield earned value schedule metrics:

Formula reminders:

\[ \mathrm{SV} = \mathrm{EV} - \mathrm{PV} \]\[ \mathrm{SPI} = \frac{\mathrm{EV}}{\mathrm{PV}} \]

Earned value metrics do not replace critical path analysis. A project can show acceptable SPI while a key milestone is at risk, especially if noncritical work is earning value while critical work is slipping.

Variance Analysis Decision Rule

When a variance appears:

1. Verify the status data.
2. Identify the driving activities and root cause.
3. Determine impact on critical and near-critical paths.
4. Assess resource, risk, cost, and scope implications.
5. Develop corrective or preventive options.
6. Recommend action with consequences.
7. Submit change requests if the approved baseline must change.
8. Communicate forecast and decisions needed.

Do not jump directly from “variance exists” to “change the baseline.”

Baselines and Change Control

Baseline vs. Current Schedule

A schedule baseline is not updated every time actual progress changes. Actuals update the current schedule; approved changes may update the baseline.

When a Change Request Is Needed

A change request is usually appropriate when:

• Scope changes affect the schedule baseline.
• A required milestone or completion date changes.
• Approved assumptions are no longer valid and baseline commitments are affected.
• Corrective action requires changes beyond the project manager’s authority.
• Contractual or stakeholder commitments are affected.
• Rebaselining is proposed.

Candidate trap: rebaselining should not be used to erase unfavorable performance history. It should follow governance and preserve traceability.

Reporting and Stakeholder Communication

Good Schedule Reporting

Effective schedule communication is tailored, concise, and decision-focused.

Report:

• Overall milestone outlook.
• Critical and near-critical path changes.
• Variances from baseline.
• Forecast completion dates.
• Key risks and uncertainty.
• Resource bottlenecks.
• External dependency status.
• Corrective actions underway.
• Decisions or approvals needed.

Avoid reporting only:

• A large unfiltered Gantt chart.
• Percent complete without forecast.
• Green/yellow/red status without explanation.
• Baseline variance without root cause.
• Technical scheduling details irrelevant to the audience.

Communication by Audience

Professional and Ethical Scheduling Behavior

PMI exams often reward professional judgment. For PMI-SP scenarios, favor answers that show:

• Transparency about uncertainty and variance.
• Accurate reporting, even when the news is unfavorable.
• Respect for approved change control.
• Documentation of assumptions and decisions.
• Collaboration with stakeholders and subject matter experts.
• Objective progress measurement.
• No manipulation of schedule data to create a misleading picture.
• Escalation when decisions exceed authority.

If an answer choice hides information, bypasses governance, manipulates dates, or blames stakeholders before analyzing facts, it is usually weak.

Scenario Decision Rules

Common Candidate Mistakes

Mistake 1: Confusing the Schedule Model with the Schedule Baseline

The model is the living calculation engine. The baseline is the approved reference. You update the model with actuals; you change the baseline only through approved change control.

Mistake 2: Treating Critical Path as Static

The critical path can change with progress, logic corrections, resource constraints, or risk events. Monitor near-critical paths too.

Mistake 3: Compressing Noncritical Work

Crashing or fast tracking noncritical activities may not improve project finish. First confirm which activities drive the target milestone or completion date.

Mistake 4: Ignoring Resource Feasibility

A logic-only schedule may look achievable while requiring the same person or equipment in multiple places at once. Resource review is part of schedule credibility.

Mistake 5: Using Percent Complete Without Remaining Duration

Percent complete can be subjective. Remaining duration and objective physical progress usually give a better forecast.

Mistake 6: Hiding Risk in Activity Durations

Undisclosed padding makes the schedule less transparent. Use documented assumptions, reserves, buffers, and risk analysis.

Mistake 7: Reporting Data Instead of Insight

A schedule professional should explain what changed, why it matters, what is forecast, and what decision is needed.

Mistake 8: Skipping Root Cause Analysis

If a milestone slips, do not immediately change the date. Determine why the variance occurred and whether corrective or preventive action is possible.

Quick Formula Review

Keep formulas connected to scenario meaning. The exam may ask what a result implies or what action should follow, not just the calculation.

High-Yield Practice Targets

After this review, use PM Mastery practice to drill these areas:

For every missed question, ask:

1. Which schedule artifact is involved?
2. Is the project planning, baselining, executing, controlling, or closing?
3. Is the issue logic, resource, risk, stakeholder, or governance-related?
4. What should a scheduling professional do before changing dates?
5. Does the answer preserve transparency and schedule integrity?

Final Rapid Review Checklist

Before you move to mock exams, confirm you can explain:

• The difference between activity list, schedule model, project schedule, and schedule baseline.
• Why a schedule with many constraints may be unreliable.
• How total float differs from free float.
• Why negative float matters.
• How resource leveling can change the critical path.
• When crashing is better than fast tracking, and when neither is appropriate.
• Why remaining duration is often more useful than percent complete.
• Why earned value schedule metrics do not replace critical path analysis.
• How to respond when actual progress differs from the baseline.
• Why rebaselining requires governance.
• How schedule risk analysis improves confidence in milestone forecasts.
• What information different stakeholders need from schedule reporting.

Practical Next Step

Use this Quick Review as a checklist, then move into original practice questions by topic. Start with CPM, schedule logic, resource optimization, monitoring and control, and change control drills. Review every missed item with detailed explanations until you can identify the scheduling issue, choose the best professional action, and explain why the tempting distractors are wrong.

Continue in PM Mastery

Use this Quick Review as a final concept map, then move into PM Mastery for focused topic drills, mixed practice sets, timed mock exams, and detailed explanations. The practice questions are original PM Mastery practice items; they are not official PMI questions, copied live-exam content, or exam dumps.