PMP Schedule, Cost, Resources, and Procurement

Study PMP Schedule, Cost, Resources, and Procurement: key concepts, common traps, and exam decision cues.

Schedule, cost, resources, and procurement are where many PMP scenarios test whether you can keep the project viable without creating downstream damage. The strongest answer balances realism, constraints, and method fit rather than forcing a single optimization.

Schedule, cost, resources, and procurement usually move together. A schedule delay may come from a supplier dependency. A cost variance may come from idle resources. A resource shortage may change the feasible schedule. A procurement decision may reduce one risk while creating another.

The exam often rewards the answer that traces the constraint before choosing the fix.

Schedule Control Starts With The Driver

Schedule pressure can come from weak estimates, missed dependencies, resource conflicts, rework, supplier delay, unclear acceptance, or unrealistic commitments. The project manager should identify the driver before applying a technique.

Crashing may help if adding resources to critical-path work is feasible and cost is acceptable. Fast-tracking may help if activities can overlap without unacceptable rework risk. Reprioritizing may help in adaptive work when lower-value scope can move later. Escalation may be needed when an external commitment or governance threshold is at stake.

The trap is choosing compression because the question says “behind schedule.” Compression is not always the answer.

Cost Signals Need Interpretation

Cost variance tells the project manager that something deserves attention. It does not, by itself, explain the cause. The project may be over budget because of approved scope, poor estimating, supplier claims, quality rework, resource inefficiency, currency or market shifts, or accelerated work.

Strong answers investigate the cause, update forecasts, and evaluate options before recommending corrective action. Reserve use, rebaselining, scope tradeoffs, procurement changes, or stakeholder escalation may be appropriate only after the cause and authority are clear.

Resources Are Capacity And Capability

Resource management is not just assigning people to tasks. The project manager must consider skill fit, availability, role clarity, competing priorities, team sustainability, onboarding, and whether adding people will actually improve flow.

On the exam, “add more resources” is often a weak answer if it ignores ramp-up time, budget, communication overhead, or whether the work is divisible. A stronger answer examines the bottleneck and chooses a response that fits the actual constraint.

Procurement Is A Delivery Strategy

Procurement affects risk, schedule, cost, quality, integration, and control. The contract type, acceptance terms, supplier monitoring, change process, and relationship model should fit the uncertainty and importance of the purchased work.

A supplier problem should not be treated as someone else’s issue. If supplier performance affects project objectives, the project manager should use the procurement management plan, contract terms, issue process, and stakeholder communication path to respond.

Integrated Constraint Thinking

Signal Stronger first question
Behind schedule What is driving the delay and is it on the critical path or flow constraint?
Over budget What caused the variance and what does the forecast show?
Resource conflict Is the issue availability, skill, priority, or role clarity?
Supplier delay What contract, dependency, risk, and integration impacts exist?

Stronger answers usually do

  • estimate and forecast using the right data and method
  • manage resources according to actual demand and constraints
  • connect procurement strategy to delivery needs and risks
  • adjust schedule or cost based on evidence, not pressure alone

Common traps

  • changing the schedule without understanding the cause of the variance
  • loading the team beyond sustainable capacity
  • treating procurement as a contract event rather than a delivery strategy
  • using historical data without checking whether it really fits the current context

Check Your Understanding

### A project is behind schedule. What should the project manager usually do before choosing crashing or fast-tracking? - [x] Identify the driver of the delay and the impact on the critical path or flow constraint - [ ] Add resources immediately - [ ] Skip quality control activities - [ ] Rebaseline without analysis > **Explanation:** Schedule responses depend on the cause and the actual constraint. ### A cost variance appears after supplier rework. What should the project manager do first? - [ ] Use management reserve immediately - [x] Analyze the cause, contract implications, forecast, and response options - [ ] Hide the variance until the next reporting cycle - [ ] Cancel the supplier without reviewing terms > **Explanation:** Cost signals need cause analysis before corrective action. ### Why is adding resources not always the best schedule response? - [ ] Extra resources are never useful - [ ] Resource management is outside the PMP exam - [x] Added resources may not address the bottleneck and can create cost, onboarding, or coordination impacts - [ ] Only the sponsor can think about resources > **Explanation:** The project manager must evaluate whether added capacity actually solves the constraint.

Sample Exam Question

Scenario: A vendor is late delivering a component needed for integration testing. Internal testers are still booked full time, costs are rising, and the sponsor asks whether the project manager can crash the schedule to protect the release date.

Question: What should the project manager do first?

  • A. Add more testers immediately to crash the schedule
  • B. Analyze the supplier dependency, critical-path impact, resource cost, contract options, and feasible recovery choices
  • C. Rebaseline the project immediately so the variance disappears
  • D. Remove integration testing from the plan to recover time

Best answer: B

Explanation: The strongest answer is B because the issue connects procurement, schedule, resources, and cost. Crashing may not help if the supplier component is the real constraint.

Why the other options are weaker:

  • A: More testers do not solve a missing supplier component.
  • C: Rebaselining before analysis hides the problem.
  • D: Removing integration testing creates quality and acceptance risk.
Revised on Monday, June 15, 2026