Try 10 focused PMI-SP questions on Schedule Strategy, with answers and explanations, then continue with PM Mastery.
| Field | Detail |
|---|---|
| Exam route | PMI-SP |
| Topic area | Schedule Strategy |
| Blueprint weight | 14% |
| Page purpose | Focused sample questions before returning to mixed practice |
Use this page to isolate Schedule Strategy for PMI-SP. Work through the 10 questions first, then review the explanations and return to mixed practice in PM Mastery.
| Pass | What to do | What to record |
|---|---|---|
| First attempt | Answer without checking the explanation first. | The fact, rule, calculation, or judgment point that controlled your answer. |
| Review | Read the explanation even when you were correct. | Why the best answer is stronger than the closest distractor. |
| Repair | Repeat only missed or uncertain items after a short break. | The pattern behind misses, not the answer letter. |
| Transfer | Return to mixed practice once the topic feels stable. | Whether the same skill holds up when the topic is no longer obvious. |
Blueprint context: 14% of the practice outline. A focused topic score can overstate readiness if you recognize the pattern too quickly, so use it as repair work before timed mixed sets.
These questions are original PM Mastery practice items aligned to this topic area. They are designed for self-assessment and are not official exam questions.
Topic: Schedule Strategy
On a predictive project with a 5-day work calendar, the data date is August 1. A 45-day critical-path activity, Integrate and validate control system, currently drives regulatory review, operator training, and site acceptance, which must support a contractual turnover milestone on October 31. After four weekly updates, the owner has reported 50%, 60%, 60%, and 75% complete, but the team still cannot forecast the three handoffs separately. Which change would best improve the schedule model for progress measurement and control?
Best answer: C
What this tests: Schedule Strategy
Explanation: The activity is too coarse to support credible forecasting because three downstream handoffs depend on it but cannot be statused separately. Breaking it into discrete, measurable deliverables with logic and interim milestones improves both progress measurement and schedule control.
Activity granularity should be detailed enough to support objective status and meaningful control, but not so detailed that the model becomes noisy and loses useful logic. Here, one 45-day critical-path activity is too coarse because it hides the internal handoffs needed for regulatory review, training, and site acceptance. That forces the team to rely on subjective percent-complete updates instead of actual finishes and remaining-duration data for each deliverable.
Decomposing the work into measurable handoff activities improves the model because it:
More frequent reporting or added constraints may make the schedule look cleaner, but they do not fix the underlying model-quality problem.
This adds the right level of detail for objective status, separate handoff forecasts, and logic-based control of the critical path.
Topic: Schedule Strategy
A construction contract requires monthly reporting on a turnover milestone due October 31, 2026. The contract states the contractor must show whether the milestone has at least 80% confidence of being met and must report the corresponding P80 forecast date. Which analysis approach should be built into the schedule management plan?
Best answer: B
What this tests: Schedule Strategy
Explanation: The contract requires a probability-based forecast, not just a deterministic status view. A schedule management plan should therefore specify schedule risk analysis, typically Monte Carlo, when the contract asks for confidence levels and P80 dates.
Contract requirements should directly shape the schedule management plan, including which analyses must be performed and reported. Here, the contract explicitly asks for two probabilistic outputs: whether the turnover milestone has at least 80% confidence of being achieved and the corresponding P80 date. Those outputs come from schedule risk analysis, commonly using Monte Carlo simulation on a credible schedule model with uncertainty and risk inputs.
Critical path, float, and milestone variance analyses are still useful, but they are deterministic control views. They can show what is driving the schedule, how much flexibility exists, or how far the forecast has moved from baseline, but they do not calculate the likelihood of meeting a date. The key takeaway is that contract language requiring confidence levels should drive the plan to include probabilistic schedule analysis.
Only probabilistic schedule risk analysis can produce both an 80% confidence assessment and a P80 milestone date.
Topic: Schedule Strategy
A project scheduler has incorporated an approved scope change into the schedule model. The update has passed logic review, and the approval authorizes a forecast update only; no rebaseline is approved. The schedule management plan requires each approved revision to be traceable for later maintenance and closeout review. What should the scheduler do next?
Best answer: B
What this tests: Schedule Strategy
Explanation: The best next step is to preserve the validated forecast update as a controlled schedule version. A version ID, data date, and link to the approved change provide the evidence needed to retrieve the right file later and explain why it changed during maintenance or closeout.
This tests schedule configuration management. Once the schedule update has been validated and approved, the next step is to store that specific revision in the controlled repository with traceable metadata. That evidence should let someone later identify the exact version, when it was current, and which approved change authorized it.
Useful evidence typically includes:
Because no rebaseline was approved, the baseline must remain the control reference. Reporting can follow, but it should be based on a preserved and traceable schedule record. Forcing milestone dates is even worse because it damages model integrity instead of documenting the approved revision.
This creates auditable configuration-management evidence so the exact approved schedule revision can be retrieved and understood later.
Topic: Schedule Strategy
An aerospace company is defining the schedule strategy for a hybrid upgrade project. The PMO maintains a schedule management plan template, standard plant-shutdown calendars, and a rule to escalate when a forecast milestone date is more than 5 working days later than its baseline date. The customer contract also requires a monthly milestone report. Which approach best uses these organizational process assets?
Best answer: B
What this tests: Schedule Strategy
Explanation: Organizational process assets should shape the schedule strategy at the start of planning. Standard templates, reusable calendars, and approved variance thresholds provide the default framework, while project-specific needs such as a contractual monthly report are added through tailoring.
OPAs are reusable internal assets that help define how the project schedule will be planned, controlled, and reported before execution begins. In this scenario, the PMO template, plant-shutdown calendars, and 5-day forecast-versus-baseline escalation rule should be used as the initial schedule strategy framework. Because the project also has a contractual monthly milestone report, the scheduler should tailor the standard approach rather than discard it. A variance threshold is a control rule for analysis and escalation; it is not current status data and it does not authorize an automatic rebaseline. The key distinction is that OPAs guide the schedule approach early, while project-specific requirements refine that approach.
OPAs should provide the default schedule template, calendars, and thresholds, then be tailored for project-specific reporting needs.
Topic: Schedule Strategy
You are developing the schedule management and reporting components of a hospital construction project plan. The contract includes a September 30 completion milestone with liquidated damages for late delivery, and the charter says any change to contractual milestones requires approved change control. For monthly status reporting, which rule should you define?
Best answer: D
What this tests: Schedule Strategy
Explanation: Contractual milestone performance should be controlled against the approved schedule baseline, not against the latest forecast. The forecast is still important, but it should be reported as the current expected date and its impact on the contractual commitment.
The key distinction is between the schedule baseline and the forecast. For a contractual milestone, the approved baseline is the official reference used to measure variance and trigger escalation or change control. The forecast is the current expected completion date based on status, so it should be communicated as schedule impact, but it does not replace the baseline.
When developing schedule-related plan components from contract requirements and project documents, define reporting rules that:
Comparing only to the prior forecast may show trend, but it does not show variance from the approved commitment.
The approved baseline is the control reference for the contractual commitment, while the forecast shows the current expected impact.
Topic: Schedule Strategy
An owner asks whether a project’s scheduling records would support a later delay claim review. Which setup most clearly shows the records are not controlled well enough for audit or forensic use?
Best answer: D
What this tests: Schedule Strategy
Explanation: Audit-ready schedule control requires a reproducible history of what the schedule model looked like at each update and why it changed. If the team overwrites prior native files and leaves the reasons only in meeting minutes, the evidence trail is too weak for reliable audit or forensic review.
The core issue is version traceability. For audit or forensic use, a reviewer must be able to reconstruct the schedule model as it existed at each data date, compare it with the approved baseline, and trace date changes to approved actions or documented status updates. Overwriting the prior native file destroys that history, and storing the rationale only in meeting minutes breaks the direct link between the model version, the change record, and the reported schedule impact.
Good control keeps earlier native files, protects issued versions from editing, separates the baseline from current forecasts, and ties status reports and change logs to specific versions. A current schedule may still be usable for day-to-day management, but it is weak evidence if prior versions cannot be reproduced.
Without preserved native versions and a traceable change record, the schedule history cannot be reliably reconstructed.
Topic: Schedule Strategy
On a hybrid medical device project, the integrated schedule now forecasts the regulatory submission milestone 15 working days late. The driving path runs through system testing and regulatory document approval; user training has 12 days of total float. During the update, the scheduler finds that workstream leads use different progress rules, no role is assigned to confirm remaining durations on handoffs, and baseline dates were changed informally after prior status meetings. What is the best corrective action?
Best answer: D
What this tests: Schedule Strategy
Explanation: The core issue is weak schedule governance: status inputs are inconsistent and baseline changes are happening informally. The best action is to clarify who owns updates and approvals, validate the driving-path data, and issue a new forecast while preserving the approved baseline unless formal change control authorizes a revision.
A late forecast should not trigger random compression or baseline replacement when the underlying schedule data are unreliable. In this scenario, unclear responsibilities are weakening both forecast credibility and baseline control. The scheduler should help establish and communicate who provides activity status, who validates remaining duration and dependency changes on the driving path, and who has authority to approve baseline changes. Once those roles are clear, the team can validate the critical update data and recalculate the forecast. The baseline must remain the approved performance reference unless a formal change is reviewed and approved.
Compressing floated work or letting the scheduler invent updates treats symptoms and further degrades control.
Clear ownership for status inputs and baseline approvals restores data quality, allowing a credible forecast while keeping the approved baseline under control.
Topic: Schedule Strategy
According to the project’s schedule management plan, activity owners provide weekly status, functional managers confirm resource availability, and the project manager decides on corrective actions. At the June 30 data date, the forecast for the regulatory go-live milestone moved from July 28 to August 1, and total float on the driving path Configure -> Validate -> Deploy is now -4 days. Before the project manager selects a recovery action, who should primarily perform the what-if analysis on the schedule model?
Best answer: A
What this tests: Schedule Strategy
Explanation: The scheduler owns technical analysis of the schedule model. In this case, status inputs are already available, so the scheduler should run the what-if analysis and explain the date impact for the project manager to decide on corrective action.
This item tests schedule role boundaries. Activity owners report actuals and remaining duration for their work, and functional managers confirm resource availability or constraints. The scheduler maintains and analyzes the schedule model, so techniques such as what-if analysis, critical path review, and float analysis belong primarily with that role. The project manager uses the scheduler’s analysis to choose corrective action, manage any needed change control, and communicate impacts. Because the milestone already shows -4 days of total float and the question asks who should perform the model-based analysis before a decision is made, the scheduler is the best choice. The closest distractor is the project manager, who owns the decision, not the detailed schedule-model analysis.
The scheduler is responsible for analyzing the schedule model, including what-if, driving-path, and float impacts, using status supplied by others.
Topic: Schedule Strategy
In a hybrid ERP rollout, the integrated test milestone is forecast 8 working days late, exceeding the 5-day variance trigger. Status data came from three teams using different cutoffs, and one team reported only percent complete without remaining duration. Before selecting recovery actions, which decision best supports consistent operational procedures and meaningful performance control?
Best answer: C
What this tests: Schedule Strategy
Explanation: When a late forecast is built from inconsistent update practices, the first control decision is to standardize schedule parameters for status collection. A single status date with required actual dates and remaining duration makes the forecast credible and keeps the variance trigger meaningful.
In schedule strategy, update parameters are operating rules that make schedule control consistent. Here, the milestone is late, but the forecast is not fully trustworthy because teams used different cutoff dates and inconsistent progress methods. The best decision is to enforce one status date for all teams and require actual dates plus remaining duration before recalculating the forecast. That produces comparable status data, preserves the approved baseline for performance measurement, and supports a meaningful recovery decision. Rebaselining would replace the control reference instead of managing the variance, hard constraints would distort the schedule model, and accelerating work with float would not improve the driving path.
A common status date and progress-entry rule creates a reliable forecast and comparable variance data before recovery decisions are made.
Topic: Schedule Strategy
During a weekly update on a construction project, some discipline leads submit remaining-duration updates, while others directly edit milestone dates in the schedule file. Several leads say they are unsure which updates are routine status entries and which date changes require formal approval. What is the best communication action for the scheduler?
Best answer: B
What this tests: Schedule Strategy
Explanation: The best response is to communicate the documented update and approval process, not just redistribute dates. A focused walkthrough of the schedule management plan clarifies who provides status, who can change schedule data, and when a date change affects only the forecast versus requiring formal approval.
When team members do not understand schedule update or approval procedures, the scheduler should use the schedule management plan to explain the process clearly. That communication should cover who submits progress data, what fields may be updated routinely, the cutoff and review steps, and which changes require formal approval through change control. The key distinction is that routine status updates may change the forecast, but they do not change the approved baseline. Sending a report does not teach the procedure, allowing uncontrolled edits weakens schedule integrity, and replacing baseline dates with forecast dates hides variance instead of controlling it. Clear process communication improves team participation and preserves reliable schedule governance.
This directly clarifies update responsibilities, status-entry rules, and when forecast changes require formal approval before any baseline change.
Use the PMI-SP Practice Test page for the full PM Mastery route, mixed-topic practice, timed mock exams, explanations, and web/mobile app access.
Read the PMI-SP guide on PMExams.com, then return to PM Mastery for timed practice.