PMI PMP: Procurement & Contract Management — Study Guide

By Laurynas Brazys · 21 July 2026 · #pmi #pmp #certification #exam-prep #study-guide

Part of the PMP — Study Guide. Practice with verified answers in the PMI exam hub, or take timed practice tests on ExamRoll.io.

Contract Types and Structuring: Matching the Instrument to the Risk

The contract type is the single most consequential procurement decision because it fixes who bears which risks and where the incentives point. Firm fixed-price (FFP) contracts push scope, schedule, and cost risk onto the seller and work well when the statement of work (SOW) is stable and well-defined — a predictive HQ office relocation with a known punch list, for example. Time-and-materials (T&M) contracts flip the risk to the buyer but provide the flexibility to respond to emerging requirements; they suit staff augmentation, discovery work, and early-stage agile development where the backlog is genuinely unknown. Cost-reimbursable variants (CPFF, CPIF, CPAF) sit between these, useful when the work is exploratory but the buyer wants incentive alignment on cost or performance targets.

The friction point on modern projects is the collision between agile delivery and fixed-price commercial expectations. Executives often want the price certainty of FFP while the delivery team needs the scope flexibility of Scrum. Signing an FFP contract for an undefined agile scope is one of the most damaging traps in procurement: the seller will either pad the price heavily to cover unknowns, refuse changes that fall outside a narrowly-interpreted SOW, or absorb losses that eventually surface as quality shortcuts and disputes. The right response is not to abandon fixed pricing but to instrument it with agile-aware controls.

Two structural controls are particularly effective:

• Scope tiers (must-have / should-have / could-have)
  • How it works: Contract commits to must-have tier; lower tiers are delivered as capacity allows
  • What it protects: Profitability and delivery certainty on core scope
• Iteration/sprint limits
  • How it works: Fixed number of sprints or a not-to-exceed total effort
  • What it protects: Prevents unbounded rework demands under “it’s agile” framing
• Change-for-change swaps
  • How it works: New backlog items require removal of equivalent-effort items
  • What it protects: Preserves the cost/schedule envelope
• Release-based pricing
  • How it works: Each release re-priced against a refined backlog
  • What it protects: Aligns commercial and delivery cadence

For a hybrid program — say, a predictive HQ move plus an agile systems migration — a single contract type rarely fits both streams. The correct structuring is often FFP for the deterministic physical move and T&M (or a tiered/capped T&M) for the migration, or a master services agreement with separate work orders per stream.

Procurement Policy, SOW, and Vendor Selection

Every procurement decision must trace back to the organization’s formal procurement policy. This is not bureaucratic hygiene — it is the mechanism that establishes authority, ensures fair competition, satisfies audit and regulatory obligations, and provides legal defensibility if a losing bidder challenges the award. A project manager who bypasses procurement to “move faster” creates personal and organizational exposure that dwarfs any schedule benefit.

The SOW is the operative document that converts intent into obligation. A defensible SOW specifies deliverables and acceptance criteria, performance standards (response times, defect thresholds, availability), reporting cadence and format, inspection and audit rights, key personnel clauses, remedies for non-performance (liquidated damages, service credits, step-in rights), and termination conditions. Vague SOWs are the root cause of the majority of downstream disputes, because ambiguity is always resolved in favor of the party whose interpretation the written words most nearly support.

Vendor selection should follow the documented evaluation criteria in the procurement plan — weighted scoring against technical capability, past performance, financial stability, cultural fit, and price. Every decision, from bidder shortlist to final award, needs to be documented with the rationale, the evaluators, and the approvals obtained. When auditors, regulators, or unsuccessful bidders come asking, the file must speak for itself.

Vendor Performance, Integration, and Dispute Resolution

Contracts do not manage themselves. Once work begins, the project manager becomes the buyer’s on-the-ground administrator of the contractual bargain. Performance monitoring means holding the seller to the reporting rhythm the SOW requires, conducting inspections and quality reviews at the contractually specified points, and formally invoking remedies when performance slips — not tolerating drift and then complaining at closeout.

Enforcement should be graduated. Early signals (a missed status report, a slipped minor milestone) warrant a documented conversation and a corrective action commitment. Repeated or material breaches trigger formal notices, cure periods, and, if unresolved, the contractual remedies: withheld payments, liquidated damages, or termination for cause. The critical PMI principle is to escalate early and evaluate alternatives before unilateral action. Terminating a vendor without first exhausting cure procedures, or walking away from a subcontractor without a continuity plan, exposes the project to both legal counterclaims and delivery collapse.

Consider a subcontractor that delivers an app meeting the SOW technically but failing a UI standard adopted after contract signature. The subcontractor is contractually correct — the new standard was not in the SOW — and their request for additional payment is legitimate. The correct response is to raise a formal change request, engage procurement and legal to amend the SOW and adjust the price and schedule, and only then authorize the rework. Insisting the vendor absorb the change is a breach; allowing the change informally without amendment is worse, because it sets a precedent that deliverables can drift without contract or payment review — and creates ambiguity about who owns the resulting defects.

Subcontractor Integration and Joint Working

Subcontractors deliver best when they are treated as part of the delivery team rather than a black box behind a contract. Effective integration includes joint kickoff working sessions, agreed ground rules for communication and decision-making, shared definitions of done and acceptance criteria, integrated backlogs or schedules, and combined risk registers. In agile contexts, subcontractor developers should participate in the same ceremonies as internal staff, with contractual language that permits this collaboration without dissolving the commercial boundary.

Amendments, Continuity, and Payment Terms

Any material change — scope, price, schedule, key personnel, acceptance criteria — must flow through a formal contract amendment executed by procurement and legal, not a side email between the PM and a vendor lead. Payment terms should be milestone-linked to acceptance rather than time-linked to invoicing, so that money follows demonstrated value.

Supplier continuity planning belongs in the risk register from day one, not after a disruption. Key questions: What happens if the vendor goes bankrupt, is acquired, or loses key personnel? Are source code escrow, documentation standards, and knowledge-transfer obligations written into the contract? Is there a qualified alternate supplier? Waiting until a supplier fails to think about continuity guarantees a project crisis; addressing it during contract structuring converts a potential catastrophe into a managed risk.

Practical Problem: Use-Case Scenario

Scenario: Meridian Financial is modernizing its customer onboarding platform, replacing a 12-year-old legacy system. The steering committee has approved a $4.2M budget over 14 months and has selected an external vendor, Northwind Digital, to deliver the build using Scrum. During contract negotiations, Meridian’s procurement director insists on a firm fixed-price (FFP) contract for the full scope to protect the budget, while Northwind’s sales lead is pushing for time-and-materials (T&M) because the product backlog contains only 40% of user stories in ready-state and integrations with three downstream systems are still being scoped.

Challenge: As project manager, you must recommend a contract structure to the procurement director that gives Meridian reasonable cost predictability without forcing Northwind to pad estimates or resist mid-sprint scope refinement.

Recommended Approach:

1. Split the engagement into two contract phases: a T&M discovery phase (approximately 6 weeks, capped at $180K) to complete backlog refinement, integration analysis, and architecture spikes before the main build begins.
2. Structure the delivery phase as a fixed-price-per-sprint arrangement — Northwind commits to a stable team of 8 practitioners at a fixed sprint price of roughly $95K per two-week sprint, with a not-to-exceed ceiling of $3.6M across 34 sprints.
3. Define the scope commercially as a prioritized backlog rather than a rigid SOW, and include a “swap clause” allowing Meridian to substitute stories of equivalent story-point size without a change order.
4. Embed exit ramps at sprints 6, 12, and 20 permitting Meridian to terminate for convenience with 30 days’ notice, protecting the budget if value delivery stalls.
5. Attach objective acceptance criteria per sprint (definition of done, automated test coverage above 80%, zero critical defects) tied to invoice approval.
6. Route the recommended structure through procurement, legal, and the sponsor with a one-page risk-allocation summary before Northwind counter-signs.

Why This Works: Matching contract type to the maturity of the requirements is a core PMI procurement principle — forcing FFP onto an undefined agile scope transfers risk in name only, because sellers price defensively or litigate change requests. The fixed-price-per-sprint model preserves cost predictability the sponsor needs while keeping backlog flexibility intact, and the discovery phase prevents both parties from committing to numbers built on assumptions rather than evidence.

← Quality Management · All domains · Project Planning →

Practice these questions → · Timed practice on ExamRoll.io →