PMI-SP — PMI Scheduling Professional Quick Reference

Last revised: June 29, 2026

Compact PMI-SP quick reference for schedule development, network logic, CPM, float, resource optimization, schedule control, EVM metrics, risk, and exam decision points.

How to Use This Quick Reference

This Quick Reference is for candidates preparing for the PMI Scheduling Professional (PMI-SP), exam code PMI-SP, from PMI. It focuses on the practical scheduling knowledge commonly tested: building a defensible schedule model, analyzing logic and float, estimating durations, managing resources, controlling baselines, communicating schedule performance, and responding to schedule risk.

Use it as a compact review sheet before deeper practice. It is independent exam-prep support and is not affiliated with PMI.

PMI-SP Scheduling Mindset

Exam mindset	What it means in practice	Common trap
Schedule is a model, not a chart	Logic, calendars, resources, constraints, assumptions, and status data drive dates	Treating a Gantt chart as the schedule model
Analyze before acting	Calculate impact, identify drivers, then recommend options	Jumping straight to crashing, escalation, or baseline change
Baselines are controlled	Approved schedule baseline changes require change control	Rebaselining to hide variance
Progress data must be credible	Actual starts/finishes, remaining duration, and data date must be accurate	Reporting percent complete without validating remaining work
Float is a management signal	Total float, free float, and negative float guide prioritization	Assuming every delayed task delays the project
Logic should reflect work	Prefer valid predecessor/successor relationships over artificial constraints	Using hard constraints or lags to force dates
Communication is tailored	Different stakeholders need different schedule views	Sending the same detailed network report to everyone
Risk is integrated	Schedule risk affects reserves, forecasts, and response plans	Treating risk as separate from the schedule

Core Schedule Artifacts

Artifact	Primary use	High-yield exam clue	Watch for
Schedule management plan	Defines how the schedule is planned, developed, monitored, and controlled	“How should scheduling be performed?”	Do not confuse with the schedule itself
WBS / scope baseline	Defines deliverables and work packages that feed activity definition	“Need to identify schedule activities”	Activities should trace to scope
Activity list	Complete list of schedule activities	“What work must be scheduled?”	Work packages are decomposed into activities
Activity attributes	Details such as predecessors, successors, resources, constraints, leads/lags	“Need more detail than activity name”	Attributes mature over time
Milestone list	Significant events or decision points	“Contract date,” “phase gate,” “major deliverable acceptance”	Milestones usually have zero duration
Network diagram	Visual or logical representation of dependencies	“Need to analyze sequence/path”	Logic quality matters more than layout
Schedule model	Data-driven model used to calculate dates	“Update the model and recalculate”	The model includes logic, calendars, constraints, durations, resources
Project schedule	Output view of planned dates	“Communicate planned start/finish dates”	A schedule view is not always the whole model
Schedule baseline	Approved version used for comparison	“Measure variance against approved dates”	Changing it needs approved change control
Schedule data	Supporting details for the schedule	“Need assumptions, constraints, resource details, alternate schedules”	Often more detailed than the displayed schedule
Resource calendars	Resource availability and working periods	“Resource unavailable,” “shift calendar,” “holiday”	Calendar errors distort dates
Risk register	Identified risks and response plans	“Schedule uncertainty,” “delay risk,” “contingency”	Link risk responses to affected activities
Issue log	Current problems requiring action	“Delay has already occurred”	A risk may become an issue
Change log	Records approved/rejected changes	“Track baseline change decisions”	Not a substitute for impact analysis
Work performance data	Raw status data	“Actual start, actual finish, remaining duration”	Must be validated before reporting
Work performance information	Analyzed performance	“Variance, trend, forecast”	Analysis turns data into management insight
Schedule forecast	Predicted future schedule performance	“Will we meet the milestone?”	Forecasts should reflect current status and risk

Schedule Management Plan: Decisions to Define

Planning decision	Examples
Scheduling methodology	Critical path method, critical chain, agile cadence, rolling-wave planning
Scheduling tool and model rules	Naming standards, coding structures, calendars, logic rules
Level of detail	Activity duration ranges, control account alignment, planning package handling
Units of measure	Hours, days, story points, elapsed time
Accuracy and precision	Rounding, estimate confidence, reporting granularity
Control thresholds	Variance thresholds that trigger analysis or action
Update frequency	Weekly, biweekly, monthly, iteration-based, milestone-based
Progress measurement	Percent complete, physical progress, earned value, milestone credit
Baseline control	Who can approve schedule baseline changes
Reporting formats	Executive dashboard, milestone chart, lookahead schedule, variance report
Reserve approach	Contingency for known risks, management reserve where applicable
Tailoring	Predictive, adaptive, hybrid, regulatory, contractual, or organizational needs

Schedule Development Flow

    flowchart LR
	A[Plan schedule management] --> B[Define activities]
	B --> C[Sequence activities]
	C --> D[Estimate resources and durations]
	D --> E[Develop schedule model]
	E --> F[Analyze network, resources, and risk]
	F --> G[Approve schedule baseline]
	G --> H[Monitor and control schedule]
	H --> I[Update actuals and forecasts]
	I --> F
	H --> J[Change control when baseline impact occurs]
	J --> G

Activity Definition and Decomposition

Concept	Use	Exam distinction
Work package	Lowest WBS component for cost/scope management	Describes deliverable-oriented work
Activity	Scheduled unit of work	Used for duration, logic, resources, and progress
Planning package	Future work not yet decomposed in detail	Supports rolling-wave planning
Rolling-wave planning	Near-term work planned in detail; future work planned at higher level	Best when details emerge over time
Milestone	Significant event, often zero duration	Measures progress or decision point, not work effort
Activity attribute	Additional scheduling metadata	Enables analysis, filtering, reporting, and control

Decomposition Checks

Every activity should trace back to authorized scope.
Activities should be small enough to estimate, assign, track, and control.
Avoid extremely long activities unless they are planning packages or summary-level placeholders.
Do not include unauthorized scope just because it helps the schedule look complete.
Clarify acceptance, handoffs, and external dependencies early.

Dependency and Logic Reference

Relationship	Meaning	Typical example	Exam caution
Finish-to-Start	Successor starts after predecessor finishes	Testing starts after build finishes	Most common, but not always correct
Start-to-Start	Successor starts after predecessor starts	Editing starts after drafting starts	May need lag for realistic overlap
Finish-to-Finish	Successor finishes after predecessor finishes	Inspection finishes after installation finishes	Useful for coordinated completion
Start-to-Finish	Successor finishes after predecessor starts	Old system stops after new system starts	Rare; do not choose unless scenario clearly fits

Dependency type	Meaning	Example	Management implication
Mandatory	Required by nature of work or contract	Foundation before walls	Hard to change without scope/technical impact
Discretionary	Preferred logic or best practice	Review before optional formatting	Candidate for resequencing or fast tracking
External	Outside project team control	Permit approval, vendor delivery	Needs monitoring, agreements, and risk responses
Internal	Within project/team control	Internal design handoff	Easier to negotiate and optimize

Leads, Lags, and Constraints

Item	Use	High-yield warning
Lead	Allows successor to start before predecessor completes	Can increase risk due to overlap
Lag	Waiting time between activities	Should represent real wait time, not hidden contingency
Constraint	Restricts start/finish date	Overuse can mask true network logic
Hard constraint	Strongly fixes a date	Can create negative float or unrealistic results
Soft constraint	Preferred target date	Less restrictive; better for planning guidance
Deadline	Target date used to calculate variance/float	Does not necessarily force the schedule date

Critical Path Method Essentials

Forward and Backward Pass

Use the exam’s stated calendar convention. If a question uses day 0 or day 1 counting, follow that convention consistently.

Forward pass:

\[ ES = \max(EF_{\text{predecessors}}), \quad EF = ES + D \]

Backward pass:

\[ LF = \min(LS_{\text{successors}}), \quad LS = LF - D \]

Total float:

\[ TF = LS - ES = LF - EF \]

Free float:

\[ FF = \min(ES_{\text{successors}}) - EF \]

Term	Meaning	Exam use
Early start	Earliest an activity can start based on predecessors	Forward pass
Early finish	Earliest an activity can finish	Forward pass
Late start	Latest an activity can start without delaying project finish or constraint	Backward pass
Late finish	Latest an activity can finish without delaying project finish or constraint	Backward pass
Total float	Time an activity can slip without delaying the project finish or constrained milestone	Prioritizes schedule risk
Free float	Time an activity can slip without delaying any immediate successor	Useful for team-level flexibility
Critical path	Longest path through the network; normally zero total float	Determines shortest project duration
Near-critical path	Path with low float close to critical	High risk; can become critical quickly
Negative float	Schedule is later than required date/constraint	Requires recovery analysis or expectation reset
Project float	Time project can slip without missing an externally imposed date	May belong to sponsor/customer, not activity owner
Driving path	Path controlling a specific milestone	Useful when milestone matters more than final finish
Longest path	Longest logical path through the project	Often used when constraints distort critical path
Critical chain	Resource-constrained critical path with buffers	Focuses on resource limits and buffer management

Duration Estimating Reference

Technique	Best when	Strength	Weakness / trap
Expert judgment	Experienced specialists are available	Fast and context-sensitive	Can be biased or undocumented
Analogous estimating	Similar past work exists	Quick early estimate	Less accurate if similarity is weak
Parametric estimating	Reliable rate or productivity factor exists	Scalable and data-based	Bad parameters produce bad estimates
Bottom-up estimating	Work is well decomposed	More detailed and defensible	Time-consuming
Three-point estimating	Uncertainty is meaningful	Captures optimistic, most likely, pessimistic	Inputs must be realistic
Data analysis	Historical records and lessons learned exist	Improves credibility	Poor data quality misleads
Reserve analysis	Risks and uncertainty need allowance	Makes uncertainty visible	Padding individual tasks hides risk

Three-Point Formulas

PERT / beta expected duration:

\[ t_E = \frac{O + 4M + P}{6} \]

Triangular expected duration:

\[ t_E = \frac{O + M + P}{3} \]

PERT standard deviation:

\[ \sigma = \frac{P - O}{6} \]

PERT variance:

\[ \sigma^2 = \left(\frac{P - O}{6}\right)^2 \]

Symbol	Meaning
O	Optimistic duration
M	Most likely duration
P	Pessimistic duration
tE	Expected duration
sigma	Standard deviation

Estimating Traps

Do not treat padding as risk management.
Do not average estimates blindly when the scenario asks for PERT.
Do not ignore resource calendars when converting effort to duration.
Effort and duration are not the same.
A full-time resource may reduce duration; adding more resources may not, especially with coordination or technical limits.
If uncertainty is high, improve assumptions, use ranges, perform risk analysis, or plan progressively.

Resource and Calendar Concepts

Concept	Meaning	Exam relevance
Effort	Labor required, such as person-hours	Used for estimating workload
Duration	Time from start to finish	Affected by calendars, availability, dependencies
Elapsed duration	Clock time regardless of working time	Useful for curing, waiting, shipping
Resource calendar	When a resource is available	Drives realistic start/finish dates
Project calendar	General working/nonworking periods	Default schedule basis
Activity calendar	Calendar specific to an activity	Needed for special shifts or constraints
Resource histogram	Resource use over time	Shows peaks and overloads
Resource breakdown structure	Hierarchical resource categories	Helps organize planning and reporting
Resource over-allocation	More work assigned than capacity	Requires leveling, smoothing, or negotiation

Resource Optimization Decision Table

Situation	Best technique	Why	Watch for
Resource demand exceeds availability	Resource leveling	Adjusts dates to resolve overloads	May extend schedule or change critical path
Need to optimize resources without changing critical path	Resource smoothing	Uses available float to even resource use	Cannot exceed available float
Scarce expert assigned to multiple critical tasks	Leveling or prioritization	Resolves impossible plan	Sponsor/functional manager may need to decide priority
Deadline cannot move but overload exists	Add resources, resequence, reduce scope, or escalate	Leveling alone may miss deadline	Must analyze trade-offs
Work can overlap safely	Fast tracking	Reduces duration by parallel work	Increases rework and coordination risk
More resources can shorten critical activity	Crashing	Trades cost/resources for time	Works only where duration is resource-sensitive
Work waits for risk event or handoff	Calendar/logic adjustment	Represents real timing	Avoid artificial lags when a better logic link exists

Schedule Compression

Technique	What changes	Best when	Main risk
Crashing	Adds resources or cost to shorten duration	Critical path activities can be shortened cost-effectively	Increased cost, diminishing returns
Fast tracking	Performs work in parallel that was planned sequentially	Dependencies are discretionary or overlap is acceptable	Rework, quality issues, coordination failure
Scope reduction	Removes or defers work	Sponsor/customer agrees to changed scope	Requires formal approval where baseline is affected
Resequencing	Changes discretionary logic	Logic is preferential, not mandatory	May introduce risk if assumptions are weak
Calendar change	Adds shifts, overtime, or workdays	Resources and policies allow it	Burnout, cost, quality, constraints
Process improvement	Removes waste or improves throughput	Bottlenecks are process-based	Benefits may be uncertain

Compression Selection Rules

Confirm the activity is on the critical path or driving path.
Identify the least disruptive option first.
Evaluate cost, risk, quality, scope, and stakeholder impact.
Recommend options; do not silently change commitments.
Use change control if baseline dates, scope, cost, or contractual commitments are affected.

Schedule Risk Analysis

Technique	Use	Output
Risk identification	Find threats and opportunities affecting schedule	Updated risk register
Qualitative risk analysis	Prioritize risks by probability/impact	Watch list, high-priority risks
Quantitative risk analysis	Numerically model uncertainty	Probability of meeting dates, confidence ranges
What-if analysis	Test alternate scenarios	Contingency plans and decision options
Monte Carlo simulation	Model many possible schedule outcomes	Date confidence curves, probabilistic finish dates
Sensitivity analysis	Identify variables with greatest impact	Tornado chart, key schedule drivers
Reserve analysis	Check adequacy of contingency	Reserve recommendations
Risk response planning	Reduce threats or enhance opportunities	Mitigation, avoidance, transfer, acceptance, exploitation

Expected monetary value, when used:

\[ EMV = Probability \times Impact \]

Schedule risk is often better expressed in time impact, probability of meeting milestones, or confidence intervals rather than only cost.

Risk response	Threat use	Opportunity use
Avoid / Exploit	Change plan to eliminate threat	Ensure opportunity occurs
Mitigate / Enhance	Reduce probability or impact	Increase probability or benefit
Transfer / Share	Shift ownership or impact	Partner to capture benefit
Accept	Take no proactive action beyond monitoring/reserve	Accept if benefit does not justify action

Earned Value and Schedule Performance Metrics

Metric	Plain formula	Interpretation
Planned Value	PV = authorized budget for scheduled work	What should have been earned by now
Earned Value	EV = budgeted value of completed work	Value of work actually completed
Actual Cost	AC = actual cost incurred	What has been spent
Schedule Variance	SV = EV - PV	Positive is ahead of planned value; negative is behind
Schedule Performance Index	SPI = EV / PV	Greater than 1 is favorable; less than 1 is unfavorable
Cost Variance	CV = EV - AC	Positive is under budget; negative is over
Cost Performance Index	CPI = EV / AC	Greater than 1 is favorable; less than 1 is unfavorable
Estimate at Completion	EAC = forecast total cost	Cost forecast, not a finish date
Variance at Completion	VAC = BAC - EAC	Expected budget variance
To-Complete Performance Index	TCPI = work remaining / funds remaining	Efficiency needed for remaining work

EVM Schedule Traps

SV and SPI are value-based, not direct calendar-day measures.
SPI can become less useful near the end of a project because EV approaches PV when all planned work is complete.
A project can have favorable cost performance and still be late.
Percent complete should be based on defined measurement rules, not optimism.
Schedule control should combine EVM, critical path analysis, milestone trends, and forecast dates.

Monitoring and Controlling Schedule

Step	What to do	Exam clue
Establish data date	Set the status point for progress measurement	“As of Friday,” “current reporting period”
Collect actuals	Actual start/finish, remaining duration, percent complete where valid	“Team reports progress”
Validate data	Check completeness, timing, and credibility	“Conflicting status reports”
Update model	Enter actuals and remaining work	“Recalculate schedule”
Check logic	Fix open ends, invalid constraints, out-of-sequence progress	“Dates look wrong”
Analyze variance	Compare current schedule to baseline	“Behind baseline”
Analyze path impact	Determine critical/driving path effect	“Will milestone be missed?”
Forecast	Predict completion dates and confidence	“Can we still meet target?”
Recommend action	Corrective/preventive actions, risk responses, change requests	“What should the scheduler do next?”
Communicate	Tailor message to stakeholders	“Sponsor wants status”
Control changes	Use formal change control for baseline changes	“Need to rebaseline”

Statusing Rules

Rule	Why it matters
No incomplete work in the past	Remaining work before the data date distorts forecasts
No actual work in the future	Actuals after the data date are invalid
Actual dates override planned dates	Status must reflect reality
Remaining duration matters	Percent complete alone does not forecast finish
Out-of-sequence progress needs review	It may show bad logic, real resequencing, or data error
Recalculate after updates	Do not interpret stale dates
Compare to baseline after model validation	Bad status data produces false variance

Baseline and Change Control Decisions

Scenario	Best next action	Avoid
Activity is late but milestone still has float	Analyze and monitor; communicate if threshold is met	Escalating as if project finish is already late
Critical path activity slips	Assess impact, forecast, identify recovery options	Updating baseline without approval
Sponsor asks to move approved finish date	Perform impact analysis and submit change request if baseline changes	Changing the schedule informally
Team reports unrealistic remaining duration	Validate with team, update assumptions, revise forecast	Accepting optimistic status without challenge
New mandatory dependency appears	Update logic, analyze impact, raise risk/issue/change as appropriate	Hiding dependency with lag
External vendor delay occurs	Update actual/forecast data, assess contractual and milestone impact, plan response	Waiting until the deadline is missed
Negative float appears	Identify driver, develop recovery options, communicate impact	Treating negative float as normal float
Scope is added	Follow integrated change control; update schedule only after authorization	Absorbing scope without schedule impact analysis
Baseline no longer useful due to approved major change	Rebaseline through approved process	Rebaselining to erase poor performance

Schedule Quality Checks

Check	What to look for	Why it matters
Missing predecessors/successors	Open starts or open finishes without justification	Weak logic hides true drivers
Excessive constraints	Must-start/must-finish dates forcing results	Reduces model credibility
Excessive lags/leads	Large or unexplained gaps/overlaps	May hide missing activities or risk
Negative float	Dates cannot meet required target	Requires recovery or expectation reset
High float outliers	Activities disconnected from real logic	May indicate missing dependencies
Long-duration activities	Hard-to-track work packages	Reduces control visibility
Invalid actual dates	Future actuals or inconsistent status	Corrupts forecast
Out-of-sequence progress	Successor progressed before predecessor complete	May require logic or status correction
Calendar mismatch	Wrong workdays, holidays, shifts	Causes inaccurate dates
Resource overloads	Assignments exceed capacity	Schedule may be infeasible
Baseline mismatch	Current schedule not comparable to approved baseline	Invalid variance analysis
Missing risk links	High-risk activities not reflected in reserves/responses	Understates uncertainty

Communication and Reporting

Audience	Useful schedule view	What they usually need
Sponsor / steering group	Milestone summary, trend chart, forecast	Decisions, exceptions, confidence
Project manager	Critical path, variance, risk, recovery options	Control actions and trade-offs
Team leads	Lookahead schedule, handoffs, constraints	Near-term priorities
Functional managers	Resource histogram, allocation forecast	Staffing conflicts and capacity
Customer / client	Contract milestones, deliverable dates, impacts	Commitment status and change implications
Vendors	Interface milestones, delivery dates, dependencies	Coordination and accountability
Agile team	Iteration plan, backlog flow, release forecast	Work sequencing and delivery predictability

Good Schedule Communication

State the data date.
Distinguish baseline dates, current forecast dates, and target dates.
Explain drivers, not just symptoms.
Show options with impacts on time, cost, scope, quality, and risk.
Escalate decisions, not raw confusion.
Do not hide unfavorable information.

Predictive, Adaptive, and Hybrid Scheduling

Environment	Scheduling focus	Common artifacts	PMI-SP exam angle
Predictive	Detailed upfront schedule baseline and control	WBS, network diagram, Gantt chart, baseline, milestone chart	CPM, float, baseline variance, change control
Adaptive / agile	Cadence, flow, prioritization, release forecasting	Product backlog, iteration plan, release roadmap, burn chart	Forecast with velocity/throughput and changing scope
Hybrid	Predictive milestones with adaptive delivery inside phases	Integrated master schedule, release plan, phase gates	Align iterative work with fixed milestones
Rolling wave	Detail near-term work; keep future work higher level	Planning packages, updated activity detail	Appropriate when uncertainty decreases over time

Agile Schedule Concepts Worth Knowing

Concept	Meaning	Scheduling use
Timebox	Fixed-duration iteration or event	Protects cadence and predictability
Velocity	Work completed per iteration	Used for release forecasting, not as a productivity weapon
Burndown chart	Remaining work over time	Shows whether team is trending toward completion
Burnup chart	Completed work and total scope over time	Shows progress and scope change
Cumulative flow diagram	Work items by workflow state	Reveals bottlenecks and WIP buildup
Lead time	Time from request to delivery	Customer-facing flow metric
Cycle time	Time actively worked from start to finish	Process efficiency metric
WIP limit	Cap on work in progress	Improves flow and reduces multitasking
Release roadmap	Forecast of features/capabilities over time	Connects agile delivery to stakeholder expectations

Velocity forecast:

\[ Iterations\ Needed = \frac{Remaining\ Backlog}{Average\ Velocity} \]

Use velocity as a planning input. Do not treat it as a guaranteed commitment when backlog size, team capacity, or priorities change.

Common “What Should the Scheduler Do Next?” Scenarios

Scenario	Best answer pattern
Requested finish date is unrealistic	Build/analyze the schedule, identify gap, propose options, communicate impact
Stakeholder wants a date commitment before analysis	Explain that commitment requires validated estimates, logic, resources, and risk review
Critical resource is unavailable	Update calendar/availability, analyze impact, evaluate alternatives, escalate if priority decision is needed
Team wants to add hidden buffer to each task	Use transparent reserve/risk planning instead
Schedule shows finish later than contract milestone	Verify model, analyze drivers, identify recovery options, communicate and use change/control processes
Many activities use hard constraints	Review and replace with logic where possible
Delay has already happened	Treat as issue; update actuals, forecast impact, plan corrective action
Delay might happen	Treat as risk; assess probability/impact and plan response
Project is behind but cost is favorable	Analyze schedule drivers; do not assume cost performance solves time performance
A manager asks to rebaseline due to poor performance	Rebaseline only through approved change control and valid justification
Agile release forecast slips	Reforecast using actual velocity/throughput, review scope priorities, communicate options
Vendor milestone is missed	Update schedule, review contract/interface impact, escalate per governance, plan mitigation
Stakeholders dispute progress	Validate measurement method, inspect objective evidence, update status transparently

High-Yield Distinctions

Do not confuse	Distinction
Schedule model vs schedule	Model calculates dates; schedule is a communicated output/view
Target date vs baseline date	Target may be desired; baseline is approved for performance measurement
Duration vs effort	Duration is calendar time; effort is labor required
Lag vs contingency	Lag is modeled waiting time; contingency is risk allowance
Risk vs issue	Risk may occur; issue has occurred
Free float vs total float	Free float protects immediate successors; total float protects project/milestone finish
Crashing vs fast tracking	Crashing adds resources/cost; fast tracking overlaps work
Leveling vs smoothing	Leveling may change finish date; smoothing stays within available float
Corrective vs preventive action	Corrective addresses current variance; preventive reduces future variance risk
Forecast vs baseline	Forecast is current prediction; baseline is approved comparison point
Percent complete vs remaining duration	Percent complete reports progress; remaining duration drives finish forecast
Milestone variance vs critical path impact	A missed milestone may or may not affect final completion

Professional Responsibility for PMI-SP Candidates

PMI-SP scenarios often reward professional schedule behavior:

Report schedule status honestly and objectively.
Do not manipulate logic, constraints, or baselines to hide variance.
Disclose assumptions, uncertainty, and confidence level.
Respect approved governance and change control.
Use historical data responsibly.
Communicate bad news early with options.
Collaborate with project managers, teams, sponsors, vendors, and functional managers.
Protect confidential project information.

Final Review Checklist

Before exam day, make sure you can quickly:

Build a simple network diagram from dependencies.
Perform forward and backward pass calculations.
Identify critical path, total float, free float, and negative float.
Choose between crashing, fast tracking, leveling, and smoothing.
Interpret schedule variance, SPI, and milestone trends.
Explain why a baseline cannot be changed informally.
Diagnose bad schedule logic, constraints, lags, and calendar issues.
Select the right report for the stakeholder.
Distinguish risk responses from issue management.
Apply rolling-wave, agile, or hybrid scheduling when the scenario calls for it.

Next step: practice PMI-SP-style scenario questions that require calculation, schedule diagnosis, and “best next action” decisions under realistic project constraints.

Scenario Guide

Schedule Strategy