Project Procurement Management (PMBOK Knowledge Area 12) is the collection of three processes that manage the acquisition of products, services or results from outside the project team. It covers Plan Procurement Management (deciding what to procure, when and how, and documenting procurement decisions in a Procurement Management Plan), Conduct Procurements (obtaining seller responses, selecting sellers and awarding contracts), and Control Procurements (managing procurement relationships, monitoring contract performance, and closing contracts). The central concept is risk allocation through contract type — the choice between fixed-price, cost-reimbursable and time-and-material contracts determines how financial risk is distributed between the buyer and seller, making procurement management inseparable from risk management.
Project procurement management is the knowledge area that most directly involves legal and commercial obligations. Every contract the project enters — with a software vendor, a construction contractor, a consulting firm, a cloud services provider — creates binding commitments that affect the project's cost, schedule, scope and risk profile. Understanding how to structure those commitments, how to select the right suppliers, and how to manage contractual relationships throughout delivery is a core project management competency.
Procurement management is also the knowledge area with the most significant external dependencies. Unlike internal team members who can be directed and managed through resource management, external suppliers must be managed through the terms of their contracts. When a supplier fails to perform, the PM cannot simply reassign their work — they must exercise contract rights, manage the commercial relationship, and potentially invoke remedies. This requires a fundamentally different management approach from internal resource management.
This guide covers all three PMBOK processes with full ITO breakdowns, the complete contract types taxonomy with risk allocation analysis, the make-or-buy decision framework, source selection criteria, the procurement lifecycle in both traditional and Agile environments, and the interrelation of procurement management with all other PMBOK knowledge areas.
Foundational Concepts
Key Concepts Before the Processes
The Buyer-Seller Relationship
In PMBOK procurement management, the project is always positioned as the buyer — the organisation acquiring goods or services. External suppliers, vendors, contractors and subcontractors are sellers. This framing is consistent throughout all three procurement processes. The PM manages procurement from the buyer's perspective — defining requirements, evaluating proposals, awarding contracts, and monitoring performance against contractual commitments.
It is important to note that the project organisation can simultaneously be a seller in a different context — if your organisation is the prime contractor on a client project, you are the seller relative to your client, but you are the buyer relative to your subcontractors. PMBOK procurement management applies to the project as buyer. The project as seller is managed through the organisation's commercial management function, not through PMBOK procurement processes.
The Make-or-Buy Decision
Before any procurement process begins, the PM must decide whether to produce work internally (make) or acquire it externally (buy). This decision is made during Plan Procurement Management and drives the entire procurement strategy.
🔨 Make (Internal Delivery)
Consider making when:
Your organisation has the required skills and capacity
The work involves proprietary knowledge or intellectual property that must remain internal
Security or confidentiality requirements prevent external involvement
The work is core to your organisation's competitive advantage
Long-term capability development is a strategic objective
Internal cost is genuinely lower than market rate when fully burdened
Your organisation lacks the required specialist skills or equipment
External supply is more cost-effective than internal development
Buying transfers risk to a supplier better placed to manage it
The work is a commodity available at competitive market rates
You need to augment internal capacity for a defined period
Faster delivery is possible through established external suppliers
You want access to technology without owning the maintenance burden
Contract Types
Contract Types — The Central Concept in Procurement Management
The choice of contract type is the single most important procurement decision — it determines how financial risk is distributed between buyer and seller, directly affects the project's cost exposure, and shapes the entire supplier management relationship. PMBOK organises contracts into three families, each with subtypes.
Risk Distribution Spectrum — Buyer vs Seller
Maximum buyer riskShared riskMaximum seller risk
Time & MaterialCost PlusFixed Price
Complete Contract Type Reference — All Families and Subtypes
Fixed-Price (FP) ContractsRisk: Seller
The buyer pays a defined price regardless of what the work actually costs the seller. The seller bears all cost overrun risk — if the work costs more than estimated, the seller absorbs the difference. Buyers prefer fixed-price contracts for well-defined work because they provide cost certainty. Sellers typically price in a risk premium to compensate for bearing this risk. Fixed-price contracts are only appropriate when scope is well-defined — using them for poorly-defined work typically results in disputes, change orders or quality compromises as the seller manages their cost exposure.
FFP — Firm Fixed Price
The purest form: a single defined price for all work. Most commonly used contract type. Buyer has maximum cost certainty; seller has maximum risk. Used for commodities, standard services, and well-defined deliverables.
FPIF — Fixed Price Incentive Fee
A fixed price with an incentive fee added if the seller achieves defined performance targets (cost underrun, early delivery, quality metrics). Shares cost savings between buyer and seller above the target cost. Motivates seller performance beyond minimum contractual compliance. Defined by a point of total assumption (PTA) above which the seller bears all additional costs.
FPEPA — Fixed Price with Economic Price Adjustment
A fixed price that includes a contractually defined adjustment mechanism for specific economic changes — typically inflation indices, foreign exchange rates, or commodity price movements — over long-duration contracts. Protects both buyer (from seller padding prices for unknown future inflation) and seller (from absorbing genuine market price changes beyond their control).
Cost-Reimbursable (CR) ContractsRisk: Buyer
The buyer reimburses the seller for all allowable, allocable and reasonable costs incurred, plus a fee (profit). The buyer bears most or all cost overrun risk — if the work costs more than estimated, the buyer pays more. Cost-reimbursable contracts are appropriate when scope is not fully defined at contract award, when work involves significant uncertainty (R&D, novel technology), or when it is genuinely impossible to define a fixed price without either the buyer or seller taking on unreasonable risk.
CPFF — Cost Plus Fixed Fee
Buyer pays all allowable costs plus a fixed fee that does not change based on actual costs. The seller has no financial incentive to reduce costs (the fee is fixed regardless) but also no incentive to over-spend (they don't earn more). Used in research, exploratory work, and situations where scope is highly uncertain.
CPIF — Cost Plus Incentive Fee
Buyer pays all allowable costs plus an incentive fee that varies based on actual vs target cost performance. If the seller completes below target cost, they share in the savings; if above, their fee is reduced. Creates cost efficiency motivation while retaining flexibility for uncertain scope. Buyer and seller agree the sharing ratio at contract award.
CPAF — Cost Plus Award Fee
Buyer pays all allowable costs plus a fee determined at the buyer's discretion based on subjective performance assessment — customer satisfaction, innovation, relationship quality. The buyer retains wide discretion and the award decision is typically not contestable. Used when performance is difficult to measure objectively but qualitative assessment is meaningful.
Time and Material (T&M) ContractsRisk: Buyer
A hybrid contract type that pays the seller a fixed daily or hourly rate (the "time" element) plus reimbursement for materials at agreed rates or actual cost (the "material" element). The total contract value is open-ended — it depends entirely on how many hours are worked and what materials are consumed. This gives the buyer maximum flexibility (work can be started or stopped at any time without penalty) but provides the least cost certainty. Most appropriate for staff augmentation, advisory services, small scope-undefined work, and emergency situations. T&M contracts almost always include a not-to-exceed (NTE) ceiling to provide the buyer some cost protection.
T&M with NTE (Not-to-Exceed)
Standard T&M augmented with a ceiling price that the buyer will not exceed. The seller must notify the buyer before reaching the NTE ceiling, at which point a decision is made to extend, reduce scope or close. Provides cost protection without converting to a fixed-price structure.
⚠️
The procurement manager's golden rule: Choose the contract type that best fits the risk profile of the work — not the contract type most comfortable for the buyer. Using fixed-price contracts for poorly-defined scope transfers risk to the seller in theory but generates disputes, change orders and quality compromises in practice, as the seller manages their cost exposure. The most expensive procurement outcome is a dispute arising from an inappropriate contract type.
The Three Processes
Project Procurement Management — The 3 PMBOK Processes
12.1
Plan Procurement Management
Planning Process Group · Documents procurement decisions, specifies the approach, identifies potential sellers
+
Plan Procurement Management is the process of documenting project procurement decisions, specifying the approach, and identifying potential sellers. It is the most analytically intensive of the three procurement processes — every subsequent procurement decision flows from the planning work done here. Its primary output is the Procurement Management Plan, supported by Procurement Strategy, Bid Documents and Source Selection Criteria.
Key decisions made in Plan Procurement Management:
Make-or-buy analysis: For each work package or component in scope, deciding whether to produce it internally or acquire it externally. The output is a formal make-or-buy decision documented in the procurement management plan.
Contract type selection: For each item to be procured, selecting the appropriate contract type based on risk profile, scope definition maturity, and the buyer's ability to define requirements precisely.
Procurement strategy: Defining the overall approach to the market — whether to use a single-source, limited competition or full competition approach; the sequencing of procurements; and the procurement method (Request for Information, Request for Proposal, Request for Quotation, Invitation to Bid).
Source selection criteria: Defining the criteria against which seller proposals will be evaluated — typically a weighted scoring model covering technical capability, experience, price, management approach, and risk assessment.
Independent cost estimates: The PM develops or commissions an independent estimate of what the procurement should cost — used to evaluate whether seller proposals represent fair value and to detect unrealistically low bids that may indicate a misunderstanding of scope or a "buy-in" strategy.
The Procurement Statement of Work (SOW) is a critical output developed in this process. The SOW describes the procurement item in sufficient detail to allow sellers to determine whether they can provide it. A poorly written SOW is the most common cause of procurement failure — ambiguous requirements lead to non-comparable proposals, change order disputes, and contractual ambiguity throughout delivery.
Inputs
Project Charter
Business Documents
Project Management Plan (Scope, Quality, Resource, Risk Management Plans)
Executing Process Group · Obtains seller responses, selects sellers and awards contracts
+
Conduct Procurements is the executing process that takes the procurement plan to market — advertising the procurement, receiving seller responses, evaluating proposals against the source selection criteria, and awarding agreements to selected sellers. The primary output is Selected Sellers and Agreements (contracts). This is the process where the legal contractual relationship between buyer and seller is formally established.
Advertising and market engagement: The bid documents (RFP, RFQ, IFB) developed in Plan Procurement Management are released to the market. For public sector procurements, advertising is typically mandatory and follows defined public procurement regulations. Bidder conferences (also called pre-bid meetings or clarification meetings) may be held to ensure all potential sellers have the same understanding of the requirements — the PM must ensure all questions and answers are shared equally with all bidders to maintain fairness.
Proposal evaluation: Seller responses are evaluated against the source selection criteria using the pre-defined weighted scoring model. Evaluations may involve technical panels, commercial panels, and management reviews. The evaluation must be conducted consistently and documented thoroughly — particularly in public sector environments where the decision may be subject to challenge or audit.
Negotiation: After preferred sellers are identified, contract negotiations confirm the final price, terms, schedule commitments, deliverable specifications and risk allocations before the contract is signed. Procurement negotiations are distinct from scope negotiations — they involve commercial terms, legal obligations, and financial risk allocation that go beyond typical project scope discussions. Legal advice is typically required for significant contracts.
Agreement types: The formal outputs of Conduct Procurements are agreements — which may take many forms: contracts, memoranda of understanding (MOUs), service level agreements (SLAs), purchase orders, or letters of intent. All represent legally binding commitments that create obligations for both buyer and seller.
Inputs
Project Management Plan (Procurement Management Plan, Scope, Requirements)
Monitoring & Controlling Process Group · Manages procurement relationships, monitors contract performance, and closes contracts
+
Control Procurements is the monitoring and controlling process that manages the buyer-seller relationship, monitors contract performance against the agreed terms, manages changes to the contract, and closes completed contracts. It runs continuously from contract award through contract close — which may or may not coincide with project close. A project may close before all its contracts are closed (where a supplier warranty period extends beyond project delivery) or a contract may close before the project does.
Contract performance monitoring: The PM tracks the seller's delivery against the contractual commitments — schedule milestones, quality standards, deliverable specifications, reporting requirements. Unlike internal team performance management, contract performance monitoring is governed by the contract terms. The PM can only hold a seller to what the contract commits them to — not to the PM's expectations or wishes. This makes the quality and completeness of the Procurement SOW (written in Plan Procurement Management) critical to effective contract control.
Claims administration: When disputes arise about whether the seller has met contractual obligations, or whether a buyer-requested change entitles the seller to additional time or cost, the claims administration process is engaged. Claims (also called disputes or constructive changes) should be resolved using the dispute resolution procedures defined in the contract. Alternative dispute resolution (ADR) mechanisms — mediation, arbitration — are preferred over litigation where possible. A well-structured contract with clear acceptance criteria and change control procedures prevents most claims before they arise.
Contract change control: Changes to a contract must go through the contract's change control procedure — which is distinct from (though aligned with) the project's integrated change control process. Not all project change requests trigger contract changes; not all contract changes are initiated by the project manager. The PM must understand which project changes have contractual implications and engage procurement management whenever a change may affect the seller's contractual obligations or entitlements.
Contract closure: Each contract must be formally closed when the seller's obligations are complete. Procurement closure involves: verifying that all deliverables have been accepted, confirming that all payments have been made, releasing any retained sums, archiving the complete contract file, and documenting lessons learned. Final payment is typically withheld until formal acceptance of all deliverables and resolution of any open claims.
Source selection criteria are the standards used to evaluate seller proposals. They must be defined in Plan Procurement Management (before proposals are received) and applied consistently to all proposals. Using pre-defined, weighted criteria prevents post-hoc rationalisation of a preferred supplier decision and ensures defensible, auditable selection decisions.
💰Price / Cost
The proposed price for the work or the total cost of ownership over the contract period. For fixed-price contracts, price is the key commercial criterion. For cost-reimbursable contracts, the proposed fee structure and estimated cost are evaluated rather than a single price. Price should rarely be the only criterion — the lowest-cost proposal often carries the highest delivery risk.
🏆Technical Capability and Approach
The seller's proposed technical solution, methodology and approach to delivering the requirements. Evaluated against the technical specifications in the Procurement SOW. A technically strong proposal from a slightly more expensive bidder may represent better value than a low-price proposal with a weak technical approach that will require extensive buyer management and change orders.
📋Relevant Experience
The seller's track record in delivering comparable work — similar scale, complexity, technology stack, industry sector or regulatory environment. References, case studies and client testimonials evidence relevant experience. Past performance on comparable work is one of the strongest predictors of future delivery performance.
👥Management Approach and Key Personnel
How the seller proposes to manage the engagement — governance structure, escalation procedures, communication approach, and the specific individuals who will lead delivery. For knowledge-work contracts (consulting, professional services, software development), the quality of the specific named individuals often matters more than the firm's general capabilities. Contracts may include key person clauses to protect against substitution of key personnel after award.
⚠️Risk Assessment
The risks associated with selecting a particular seller — financial stability, supply chain dependencies, single points of failure, concentration risk (too much of your project dependent on one supplier), geographical risk, and the seller's own risk management approach. A financially unstable seller creates delivery risk regardless of how compelling their proposal is.
⚡Capacity and Schedule Commitment
Whether the seller has the capacity to deliver the required work within the project's timeline — given their current commitments to other clients. A seller who wins the contract but cannot resource it adequately because they are overcommitted elsewhere is a major schedule risk. Realistic schedule proposals with credible resource plans should be weighted more highly than aggressive schedules that will require change order renegotiation.
Interrelation to Other Knowledge Areas
How Procurement Management Connects to Every Other Knowledge Area
🔗KA01 — Integration Management
Procurement Management is deeply integrated with the overall project management plan. The Procurement Management Plan is a subsidiary component of the Project Management Plan, and all procurement decisions must align with integrated change control. When a scope change has contractual implications, the PM must coordinate between the project change control process and the contract change control procedure. Contract close-out must be coordinated with project close — the project cannot formally close while contracts remain open. Lessons learned from procurement activities feed into the project's OPAs through integration management.
📐KA02 — Scope Management
The Procurement SOW is derived directly from the Scope Baseline — the work packages in the WBS that are being procured externally. The quality and precision of the Procurement SOW determines the quality of proposals received and the clarity of contractual obligations. Every scope change that affects a contracted work package must be assessed for contractual impact — additional scope given to a fixed-price supplier triggers a change order; reduced scope may trigger a claim for lost profit. Control Scope and Control Procurements must work in parallel to prevent scope changes from creating unresolved contractual ambiguity.
📅KA03 — Schedule Management
Supplier delivery dates are external dependencies that must be incorporated into the project network diagram. The procurement lead time (from RFP release to contract award) is itself a schedulable activity that must be planned and tracked. Supplier milestones on the critical path represent concentrated schedule risk — a late supplier delivery delays the project by the same amount. T&M contracts create less schedule pressure on suppliers than fixed-price contracts; conversely, delay penalties (liquidated damages clauses) in fixed-price contracts provide contractual schedule enforcement. Schedule slippage by the supplier should trigger the contract's change management procedure.
💰KA04 — Cost Management
Contract type selection is fundamentally a cost risk management decision. Fixed-price contracts provide buyer cost certainty but at a premium (seller risk loading). Cost-reimbursable contracts give the buyer full visibility of actual costs but transfer all cost overrun risk to the buyer. T&M contracts are the most cost-uncertain — the final cost depends entirely on the work volume consumed. Supplier invoices flow directly into Actual Cost (AC) for EVM analysis. Contract change orders must be assessed for cost impact before approval. Retention sums, payment milestones and performance bonds are all financial tools that connect procurement and cost management.
⭐KA05 — Quality Management
Supplier quality is an extension of project quality management. The contract must include quality requirements, acceptance criteria, inspection rights, and non-conformance remedies — otherwise the PM has no contractual mechanism to enforce quality standards on suppliers. Incoming inspection of supplier deliverables (an appraisal cost in the Cost of Quality framework) is a Control Quality activity applied to procured items. Supplier audits (a Control Procurements tool) verify that the supplier's quality management processes meet contracted standards. Non-conforming supplier deliverables generate change requests in both Control Procurements and Control Quality.
👥KA06 — Resource Management
The make-or-buy decision is intrinsically linked to resource management — the decision to buy is often driven by a resource gap (skills or capacity not available internally). Procured resources (contractors, consultants) are managed through their contracts, not through the same management processes as internal team members. Key person clauses, substitution approval requirements, and supplier mobilisation plans are procurement mechanisms that address resource management concerns. When a supplier underperforms due to inadequate resourcing, the remedies available to the PM are contractual (not direct management authority).
⚠️KA08 — Risk Management
Contract type selection is the primary mechanism for transferring project risk to suppliers. Fixed-price contracts transfer cost risk to the seller; cost-reimbursable contracts retain it with the buyer. The Risk Register is a key input to Plan Procurement Management — identified risks inform which contract types are appropriate and what contractual risk protections to include. Specific procurement risk mechanisms include: performance bonds (compensate buyer if seller defaults), liquidated damages (pre-agreed daily penalty for late delivery), warranties (seller's liability for defects post-delivery), and indemnification clauses (protection against third-party claims arising from supplier actions). Risk concentration (over-dependence on a single supplier) is itself a procurement risk requiring management.
📣KA07 — Communications Management
Supplier communications must be carefully managed — informal communications that could be interpreted as instructions or scope changes create contractual exposure. The contract should define the formal communication channels (who can instruct the supplier, in what format, with what authority), the reporting requirements (frequency, format, content), and the escalation procedures for disputes. Progress meetings, site visits, and performance reviews are all contractual communication events. Any instruction given to a supplier outside the defined formal channels may be inadmissible in a dispute or may create contractual obligations that were not intended.
🤝KA10 — Stakeholder Management
Sellers are stakeholders — they have interests, concerns and influence that must be managed like any other project stakeholder. The stakeholder register should include key supplier contacts and their engagement level. During the conduct procurements process, supplier communications require careful stakeholder management — maintaining equal treatment of all bidders, managing competitive sensitivity, and building collaborative relationships with selected suppliers without compromising contractual objectivity. Post-award relationship management with key suppliers is as important as pre-award evaluation in determining delivery success.
Agile and Hybrid Approaches
Procurement Management in Agile, Waterfall and Hybrid Environments
🏛️ Procurement in Waterfall (Predictive)
Traditional waterfall procurement follows the full three-process PMBOK model with formal competitive tendering:
Complete Procurement SOW developed from the full WBS before market engagement
Fixed-price contracts preferred — scope is defined, cost certainty is possible
Milestone-based payment schedules aligned to project stage gates
Formal change control process for all contract modifications
EVM applied to supplier performance (earned value of delivered work vs planned value)
Dispute resolution procedures invoked for non-performance
Public sector: full procurement regulations apply (OJEU, PCR, utilities procurement)
Key challenge: Traditional procurement timelines (6–18 months for major contracts) can be a significant constraint on project schedule, particularly in public sector environments where procurement regulations are mandatory.
🔄 Procurement in Agile
Agile procurement requires different contract structures to accommodate iterative, evolving scope:
Fixed-price contracts are difficult in pure Agile — scope is not fully defined at contract award
T&M contracts are the most common Agile procurement vehicle — the team is bought, not the output
Outcome-based contracts: fixed price for a defined set of outcomes, with flexibility on how they are achieved
Sprint-based payment: monthly or sprint-by-sprint invoicing based on team cost rather than deliverable milestones
Shorter initial contracts with extension options — allows relationship assessment before full commitment
Collaboration-focused contracts: shared incentives aligned to project success rather than adversarial fixed-price risk transfer
The Definition of Done becomes the contractual acceptance criterion at sprint level
Agile supplier selection emphasises team capability and collaboration behaviours over lowest price
Key challenge: Most procurement regulations and public sector frameworks are designed for defined-scope fixed-price contracts — adapting them for Agile procurement requires active navigation of regulatory requirements.
Hybrid Procurement Approaches
Hybrid procurement maintains formal governance and competitive selection at the programme level, while using more flexible commercial structures for delivery. Common hybrid approaches include: framework agreements (pre-qualifying a panel of suppliers through a competitive process, then calling off work under T&M or outcome-based terms as needs are defined), alliance contracting (risk-and-reward sharing between buyer and multiple suppliers, with collective incentives to deliver programme outcomes), and early contractor involvement (ECI) (engaging the contractor during design to build in constructability, cost certainty and risk allocation before the full delivery contract is awarded).
Exam Tips
Procurement Management — 7 Exam Tips for PMP and APM PMQ
1
Know which contract type puts risk on the buyer vs seller. Fixed-price = seller bears cost overrun risk. Cost-reimbursable = buyer bears cost overrun risk. T&M = buyer bears volume risk (open-ended cost). This is one of the most frequently tested procurement concepts on the PMP exam. Any scenario describing a situation where the buyer wants cost certainty points to fixed-price; uncertainty or evolving scope points to cost-reimbursable or T&M.
2
Fixed-price contracts are not always best for the buyer. A common PMP trap is assuming buyers always prefer fixed-price. For poorly-defined scope, fixed-price contracts create perverse incentives — the seller manages their cost exposure through change orders, quality compromises or scope disputes. The right contract type matches the risk profile of the work. The exam tests this nuance.
3
Know all three Fixed-Price subtypes and their distinguishing features. FFP (single fixed price), FPIF (fixed price plus performance incentive with a Point of Total Assumption), FPEPA (fixed price with economic adjustment clause for long-duration contracts). The PMP exam describes a scenario and asks which contract type applies — know the specific conditions that distinguish each.
4
The Point of Total Assumption (PTA) appears in FPIF contracts. Above the PTA, the seller bears 100% of additional costs — the fixed-price ceiling has effectively been hit. Below the PTA, cost overruns are shared between buyer and seller at the agreed sharing ratio. PTA = ((Ceiling Price − Target Price) / Buyer's Share Ratio) + Target Cost. This formula is occasionally tested on PMP.
5
Bidder conferences must treat all bidders equally. Any question asked by one bidder at a conference must be shared with all bidders. Any answer given privately that is not shared with all bidders creates grounds for a procurement challenge. The exam tests whether candidates understand that equal treatment of bidders is a procurement management obligation, not just good practice.
6
Sellers are stakeholders. The PMP exam takes a broad view of stakeholders that explicitly includes suppliers and contractors. Procurement relationships are stakeholder relationships governed by contracts. Questions about managing difficult suppliers, late deliveries or contract disputes are procurement management questions — the answer must work within the contract framework, not ignore it.
7
Contract close ≠ project close. A procurement can be closed before the project is complete (the supplier's work is done while the project continues). A procurement can remain open after a project appears complete (warranty periods, defects liability periods). The exam tests whether candidates understand that procurement closure is a separate administrative activity from project closure, managed through Control Procurements, not through Close Project or Phase.
Apply This Knowledge Area in Your PMP or APM PMQ Exam
Procurement management processes, contract types and source selection are examined across both the PMP and APM PMQ. Contract type risk allocation is one of the most frequently tested PMP scenarios.
The three PMBOK processes in Project Procurement Management (Knowledge Area 12) are: (1) Plan Procurement Management (Planning Process Group) — deciding what to procure, when, how and from whom. Key outputs include the Procurement Management Plan, Procurement SOW, Bid Documents, Source Selection Criteria, and Make-or-Buy Decisions. (2) Conduct Procurements (Executing Process Group) — taking the procurement to market, receiving and evaluating seller proposals, negotiating, and awarding contracts. Key outputs are Selected Sellers and Agreements (contracts). (3) Control Procurements (Monitoring and Controlling Process Group) — managing the buyer-seller contractual relationship, monitoring seller performance, managing contract changes, administering claims, and formally closing completed contracts. Key outputs include Closed Procurements and Work Performance Information. Unlike most other knowledge areas, procurement management has only three processes — but they span all process groups from Planning through Monitoring and Controlling.
Fixed-price contracts commit the seller to deliver a defined scope for a defined price, regardless of what the work actually costs. The seller bears all cost overrun risk — if the work costs more than they priced, they absorb the difference. Buyers prefer fixed-price contracts for well-defined work because they provide cost certainty. Cost-reimbursable contracts reimburse the seller for all allowable costs incurred, plus a fee. The buyer bears cost overrun risk — if the work costs more than estimated, the buyer pays more. Cost-reimbursable contracts are appropriate when scope is not fully defined, when work involves significant uncertainty, or when it is impossible to establish a fair fixed price without one party taking on unreasonable risk. The choice between them is fundamentally a risk allocation decision: who is better placed to manage the cost uncertainty of this specific piece of work?
A Procurement Statement of Work (SOW) is a document that describes the procurement item — the product, service or result to be acquired — in sufficient detail to allow potential sellers to determine whether they are capable of providing it and to prepare a credible proposal. It typically defines: what is to be delivered (deliverables, specifications, quantity), how it is to be delivered (methodology requirements, standards, constraints), when it is to be delivered (schedule requirements, milestones), where it is to be delivered (location, deployment environment), and the acceptance criteria against which deliverables will be evaluated. A poorly-written SOW is the most common cause of procurement failure — ambiguous requirements produce non-comparable proposals, post-award disputes, and contractual ambiguity throughout delivery. The Procurement SOW is derived from the WBS scope baseline and becomes part of the contract once the supplier is selected.
The make-or-buy decision is the analysis of whether to produce a product or perform a service internally (make) or acquire it from an external supplier (buy). It is one of the key analytical activities in Plan Procurement Management. Factors favouring internal production (make) include: availability of required skills and capacity internally, proprietary knowledge that must remain confidential, regulatory requirements mandating internal execution, strategic importance to long-term capability development, and situations where internal cost is genuinely lower than market rates when fully burdened with overhead. Factors favouring external procurement (buy) include: lack of internal skills or capacity, access to specialist expertise not economically feasible to develop internally, cost-efficiency of market supply, risk transfer benefits of a well-structured contract, and the desire to focus internal resources on core activities while procuring support services. The make-or-buy decision must be formally documented as it directly determines the procurement scope and strategy.
Agile procurement requires different commercial structures from traditional fixed-price contracting because Agile projects deliberately defer full scope definition. The most common Agile procurement approach is time-and-material contracting — the buyer purchases the supplier's team capacity (a defined team for a defined daily or monthly rate) rather than a defined set of deliverables. This aligns with Agile's principle of fixed cost and time with variable scope. Other Agile-friendly procurement approaches include outcome-based contracts (fixed price for defined outcomes with flexibility on how they are achieved), sprint-based milestone payments (invoicing on sprint completion rather than predefined deliverable milestones), and shorter initial contracts with extension options (allowing relationship assessment before full commitment). The Definition of Done becomes the contractual acceptance criterion at sprint level — making clear quality standards and acceptance processes even more important in Agile procurement than in traditional approaches.
The Point of Total Assumption (PTA) is a concept specific to Fixed Price Incentive Fee (FPIF) contracts. It represents the cost at which the seller begins to bear 100% of additional cost overruns — above the PTA, the contract effectively becomes a firm fixed-price contract from a risk perspective. Below the PTA, cost overruns above the target cost are shared between buyer and seller at the agreed sharing ratio (for example, 80% buyer / 20% seller). Above the PTA, the seller absorbs all additional costs because they have already reached the contract ceiling price. The PTA formula is: PTA = ((Ceiling Price − Target Price) ÷ Buyer's Share Ratio) + Target Cost. The PTA is important because it defines the cost level at which the seller's incentive to control costs shifts — below PTA they share overrun pain with the buyer; above PTA they bear it entirely. This is a periodic PMP exam topic when FPIF contracts appear in scenarios.