Try 10 focused PMI-SP questions on Schedule Planning and Development, with answers and explanations, then continue with PM Mastery.
| Field | Detail |
|---|---|
| Exam route | PMI-SP |
| Topic area | Schedule Planning and Development |
| Blueprint weight | 31% |
| Page purpose | Focused sample questions before returning to mixed practice |
Use this page to isolate Schedule Planning and Development 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: 31% 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 Planning and Development
As of September 20, the approved launch milestone is October 15. The driving path has 6 working days of system testing remaining, then an 8-day vendor security review, then 4 days of deployment prep. All remaining durations are validated as minimum feasible and cannot overlap. The project calendar has 16 working days left before October 15, and a separate training activity has 10 days of total float. What is the best scheduler action?
Best answer: C
What this tests: Schedule Planning and Development
Explanation: Milestone achievability is determined by the driving path, validated durations, and available working time. Here, 18 days of remaining driving work must fit into 16 working days, and the work cannot be shortened or overlapped, so the date should be reforecast and handled through escalation and change control.
The key test is whether the current schedule model can still produce the milestone date. In this scenario, the driving sequence still requires 18 working days of remaining effort, but only 16 working days remain before the approved milestone. Because the durations are already validated as minimum feasible and the work cannot overlap, the date is not achievable in the current model. The proper scheduler response is to keep the model realistic: update the forecast to the later date, communicate the variance, and follow change control if the committed milestone or baseline must be revised.
Shortening the separate training work would not help because it has float and is not driving the launch milestone.
The driving path needs 18 days against 16 available, so the milestone is not achievable without an approved change.
Topic: Schedule Planning and Development
As of the status date of September 18, 2026, three remaining finish-to-start paths on the same Monday-Friday calendar merge into milestone M7. M7 has no date constraints or manual date overrides.
Path to M7 | Total float | Monte Carlo chance of driving M7 |
|---|---|---|
A-B-C | 0 days | 56% |
D-E-F | 1 day | 38% |
G-H | 6 days | 6% |
Which interpretation best identifies the critical and near-critical paths?
A-B-C and D-E-F as critical paths.A-B-C is critical; D-E-F is near-critical.A-B-C matters because D-E-F has float.Best answer: B
What this tests: Schedule Planning and Development
Explanation: With one shared calendar and no milestone constraints, the zero-float path is the current critical path. The 1-day-float path is near-critical because it has very little schedule protection and still drives the milestone in many Monte Carlo iterations.
In an unconstrained CPM network, the critical path is the path with zero total float that currently drives the milestone. Here, A-B-C is critical because it has 0 days of float. D-E-F is near-critical because it has only 1 day of float and still drives M7 in 38% of Monte Carlo runs, meaning a small slip could make it the driving path. Because all paths use the same calendar and the milestone has no manual constraints, the float comparison is reliable.
A path with 6 days of float and only 6% driving likelihood is not near-critical under these facts.
It correctly uses zero total float for the current critical path and low float plus high driving likelihood for the near-critical path.
Topic: Schedule Planning and Development
During schedule validation, the project uses a Monday-Friday calendar and the status date is close of business June 6, 2025. The driving path to the contractual milestone Site Ready is Procurement closeout (4 working days remaining) -> FS -> Installation (5 days remaining) -> FS -> Commissioning (3 days remaining) -> FS -> milestone, which has a finish-no-later-than June 20, 2025 constraint. A schedule risk review shows a 60% chance that regulator availability will add 2 days to Commissioning. Which assessment is most appropriate?
Best answer: D
What this tests: Schedule Planning and Development
Explanation: Milestone achievability should come from the logic-driven forecast, not the desired target date. Starting after the June 6 status date, the 12 working-day driving path finishes on June 24, so the June 20 milestone is already unachievable even before the added risk is considered.
A milestone is achievable only if the logic-driven schedule can reach it on the stated calendar. Here, the status date is close of business June 6, so the remaining driving-path work starts on the next working day, June 9. The path has 12 working days remaining: 4 days for Procurement closeout, 5 for Installation, and 3 for Commissioning. On a Monday-Friday calendar, that forecasts the milestone on June 24, which is already later than the June 20 contractual date. The regulator-availability risk could add two more days, lowering confidence further, but it is not needed to prove the miss. Good schedule practice is to preserve the real logic and report the later forecast, not to force dates or insert artificial overlap. Hiding the miss makes the model look cleaner but weakens forecast credibility and traceability.
With 12 working days remaining after the June 6 status date, the earliest logic-based finish is June 24, so the June 20 milestone is already missed.
Topic: Schedule Planning and Development
A scheduler for a data center upgrade has identified activities, drafted logic, and estimated durations. Required roles include network engineers, electricians, and vendor technicians, but the draft schedule assumes they are all available full time; functional managers and team members have not yet confirmed calendars or assignment windows. What should the scheduler do next?
Best answer: A
What this tests: Schedule Planning and Development
Explanation: The next step is to make the resource assumptions credible. Developing the resource breakdown structure and confirming actual availability, calendars, and assignment windows with functional managers and team members provides the basis for reliable assignments and dates.
In schedule planning and development, resource loading should be based on validated availability, not default assumptions. After activities, logic, and duration estimates are drafted, the scheduler should organize needed resources in a resource breakdown structure and confirm when those resources can actually support the work. Functional managers help verify shared-resource capacity and calendars, while team members can confirm realistic assignment windows and constraints.
Without that validation, later actions such as resource leveling, schedule optimization, or baselining are built on weak data and may produce misleading dates. Sending a staffing report also does not solve the planning problem; it only communicates an unverified assumption. The best sequence is to confirm resource availability first, then refine assignments, analyze impacts, and finalize the schedule.
A credible schedule needs confirmed resource categories, calendars, and availability before assignments, leveling, or baselining.
Topic: Schedule Planning and Development
A team is developing the schedule baseline for a facilities upgrade. The contract requires mechanical completion by September 30, and any change to that date needs approved change control. The draft schedule includes durations, but several vendor-delivery and commissioning activities are not logically linked, and the same commissioning crew is assigned to two sites in the same week. The sponsor wants to tell the client the deadline is achievable. What is the BEST action?
Best answer: C
What this tests: Schedule Planning and Development
Explanation: The best evidence is a validated schedule model, not optimism or a forced date. Before claiming the contractual milestone is achievable, the scheduler should confirm complete logic and realistic resource availability, then analyze the driving path to the required deadline.
To support a claim that a required deadline is achievable, the schedule must provide objective evidence. In this case, the draft model is not yet reliable because key vendor and commissioning dependencies are missing and the same crew is double-booked. The best action is to correct those schedule-model weaknesses first, then test whether the contractual milestone is still met.
Useful evidence includes:
That is stronger than opinion, a cosmetic milestone chart, or a date constraint. A forced constraint may make the date appear achievable without proving the work sequence and resources actually support it.
A required deadline is supportable only when a logic-driven, resource-feasible schedule model shows the contractual milestone can be met.
Topic: Schedule Planning and Development
As of July 8, 2026, two projects in the same program use a Monday-Friday calendar. Project Beta’s System Integration activity is scheduled to start July 21, but it cannot begin until Project Alpha completes the external milestone API environment ready and handed over. Alpha now forecasts that milestone for July 24, while Beta’s schedule currently uses a Start No Earlier Than July 21 constraint. What should the scheduler do to improve schedule model quality?
Best answer: B
What this tests: Schedule Planning and Development
Explanation: This is an inter-project dependency, so it should be modeled as logic in the schedule, not as a hard-coded date. Linking Beta’s activity to Alpha’s handoff milestone keeps the integrated schedule traceable and makes the forecast credible as dates change.
When work in one project cannot start until a deliverable or milestone from another project is complete, the dependency should appear explicitly in the schedule model. Here, Beta’s integration is driven by Alpha’s API environment ready and handed over milestone, so the proper fix is to replace the Start No Earlier Than constraint with an external predecessor relationship, typically finish-to-start unless the work pattern says otherwise. That keeps the integrated master schedule aligned with real execution logic, updates the forecast automatically when Alpha moves, and makes downstream impact visible. A date constraint, arbitrary lag, or off-model tracking may make the schedule look cleaner, but those approaches hide the true driver and weaken forecast credibility. The model should show what actually controls the start date.
An explicit external logic link preserves traceability and lets Beta’s forecast move automatically with Alpha’s milestone.
Topic: Schedule Planning and Development
During planning for a hospital system rollout, the sponsor says, “Since the forecast will change every month, let’s use the latest forecast as our baseline.” The team has already completed scope, schedule, and cost baselines. Which response best explains how the performance measurement baseline enables performance measurement and management?
Best answer: D
What this tests: Schedule Planning and Development
Explanation: The performance measurement baseline is the approved integrated reference for measuring project performance. Forecasts are updated expectations based on current status, but they do not replace the baseline used to assess variance and control change.
The key distinction is baseline versus forecast. The performance measurement baseline combines the approved scope, schedule, and cost baselines into the control reference for the project. During execution, actual performance and current forecasts are compared against that approved reference to identify variance, evaluate trends, and support corrective action or formal change control. A forecast shows the latest expected outcome based on current status; it is not the benchmark for judging performance. If the team keeps replacing the baseline with the latest forecast, variance disappears on paper and management loses visibility into how the project is performing against the authorized plan. A schedule-only baseline is also insufficient because performance measurement must stay integrated across scope, schedule, and cost.
A PMB is the approved integrated reference used to compare actuals and forecasts against the authorized plan and manage changes.
Topic: Schedule Planning and Development
An approved schedule baseline includes a contractual system-demo milestone on September 30; moving it requires approved change control. Next week, one validation engineer is assigned to a critical-path test-prep activity and to two noncritical integration tasks, and the integration tasks each have 4 days of total float. There is no budget for extra resources, and the technical dependency sequence is fixed. What is the best scheduling action?
Best answer: D
What this tests: Schedule Planning and Development
Explanation: Resource smoothing is the best fit when you need to reduce a resource peak without changing the project finish date. Here, the overallocated work has available float, the milestone cannot move without approval, and neither logic changes nor acceleration are justified.
This situation calls for resource smoothing because the project must keep a fixed contractual milestone and the overloaded work can be shifted within existing total float. The two integration tasks are noncritical and each has 4 days of float, so their timing can be adjusted to reduce the validation engineer’s peak demand without changing the finish date or the approved dependency logic.
The key distinction is the scheduling effect: smoothing preserves the milestone, while leveling may move it.
Smoothing uses available float to relieve the overallocation while keeping the fixed milestone and approved logic unchanged.
Topic: Schedule Planning and Development
A scheduler for a hospital system implementation has built the draft schedule model from the WBS, calendars, and dependencies. Team members have validated activity logic and durations, and the critical path is credible. The customer and sponsor still disagree on two contractual milestone dates, but the project manager wants to freeze the baseline this week. What should the scheduler do next?
Best answer: B
What this tests: Schedule Planning and Development
Explanation: An approved schedule baseline requires stakeholder agreement on the dates that will be used for control. Since the schedule model is technically sound but milestone commitments are still disputed, the next step is to resolve those differences and obtain formal approval.
In PMI-SP practice, the schedule baseline is established only after the draft schedule model is both credible and accepted by the parties who must commit to it. Here, the team has already validated activity logic, durations, and the critical path, so the remaining gap is consensus on the disputed contractual milestones. The best next step is a baseline review with the customer, sponsor, project manager, and team members to confirm assumptions, resolve the milestone disagreement, and formally approve the dates.
Once that approval is in place, the baseline becomes the reference for future schedule measurement and control. Freezing draft dates early, reporting them as if final, or using rebaseline language before an initial baseline exists would undermine proper schedule governance.
A baseline should be approved only after the validated schedule model and milestone commitments are jointly accepted by the key stakeholders.
Topic: Schedule Planning and Development
On a predictive facility-upgrade project, the status date is August 12 and all remaining activities use a Monday-Friday calendar. The contract requires the Ready for Operations milestone on August 30. After statusing, the driving path is equipment startup (4 days remaining) -> performance test (5 days) -> client witness (3 days), and client witness has a finish-to-start dependency because the client will attend only after testing is complete. The milestone now forecasts September 4 with -3 days total float. The project manager asks the scheduler to make the schedule show August 30. What is the best response?
Best answer: D
What this tests: Schedule Planning and Development
Explanation: When a forecast misses a contractual milestone, the scheduler should preserve a truthful schedule model and make the variance visible. Validate the driving path and current status, then propose realistic recovery or formal change-control actions instead of forcing dates or breaking logic.
Contractual milestones should remain visible in the schedule, but the forecast must still come from current status, valid logic, calendars, and realistic remaining durations. In this case, the finish-to-start link to client witness is explicit, and the Monday-Friday calendar plus remaining work already produce a September 4 forecast. Forcing the milestone to August 30 with a hard constraint, artificial lead, or baseline change would make the report look cleaner but would weaken traceability and distort the driving path. The scheduler should confirm the status data, keep the commitment date for variance comparison, and analyze credible recovery options or escalate through formal change control if recovery is not feasible. A clean-looking schedule is not useful if the forecast is no longer believable.
This keeps the forecast truthful and traceable while addressing the contract conflict through recovery analysis or formal control, not cosmetic edits.
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.