
Performance Obligates Process: Contractual Delivery in Procurement Management
PMBOK v8 Definition
A contract is "a mutually binding agreement that obligates the seller to provide the specified product, service, or result and obligates the buyer to pay for it." This concept is directly linked to continuous delivery, defined as "the practice of delivering feature increments immediately to customers, often through the use of small batches of work and automation technology." Performance obligates the process by requiring immediate delivery of increments to customers, making contract performance a binding, ongoing obligation rather than a final event.
Why It Matters for the Exam
This concept appears frequently in procurement management questions, particularly those testing the distinction between contract types and performance obligations. PMI exam questions often present scenarios where a buyer expects incremental delivery, and you must identify the appropriate contract type or recognize that performance obligations are triggered by delivery, not by contract signing. Expect this in situational questions about seller selection, contract administration, and dispute resolution.
Key Points to Remember (for the exam)
-
Core Definition: A contract obligates the seller to provide the specified product/service/result AND obligates the buyer to pay for it—both parties have binding duties.
-
Performance Trigger: Performance obligations are activated when increments are delivered to customers, not when the contract is signed. Continuous delivery uses small batches and automation.
-
Contract Types Tested: Time and Materials (T&M) contracts are "a hybrid contractual arrangement containing aspects of both cost-reimbursable and fixed-price contracts"—frequently confused with pure cost-reimbursable or pure fixed-price.
-
Procurement Process Stages: Seller selection should be "based on predefined criteria such as cost, quality, and the seller's ability to meet the project requirements and timelines." Contract negotiation follows selection.
-
Monitoring & Controlling: "Managing procurement relationships, monitoring contract performance, and making necessary changes and corrections" is the final procurement stage. Issues must be addressed promptly.
-
Common Confusion: Confusing contingency reserve (time/money for known risks with active response strategies) with management reserve (for unknown risks). Only contingency reserve is part of the cost baseline.
-
Key Risk Term: A threat is "a risk that would have a negative effect on one or more portfolio, program, or project objectives"—distinct from an opportunity.
Typical PMI Exam Example
A project manager signs a T&M contract with a software vendor to develop a customer portal. The vendor delivers a working login feature after two weeks (small batch). The buyer must pay for this increment immediately. Which concept does this scenario BEST illustrate?
Answer: Performance obligates process—the contract obligates the seller to deliver increments and the buyer to pay for them as delivered, not at project completion.
PMI Exam Traps
-
Trap: Confusing continuous delivery with final delivery at project end. Reality: Continuous delivery means "delivering feature increments immediately to customers," often using small batches and automation—not waiting until project closure.
-
Trap: Thinking a contract is finalized before seller selection. Reality: "Once a seller is selected, the contract is negotiated and finalized"—selection comes first, then contract terms.
-
Trap: Confusing contingency reserve with management reserve. Reality: Contingency reserve is "time or money allocated in the schedule or cost baseline for known risks with active response strategies." Management reserve is for unknown risks and is NOT in the baseline.
-
Trap: Assuming T&M contracts are purely cost-reimbursable or purely fixed-price. Reality: T&M is "a hybrid contractual arrangement containing aspects of both"—it has cost-reimbursable elements (materials at cost) and fixed-price elements (labor at fixed rates).
Important PMI Connections
| Related Concept | Relationship Type | Exam Attention Point |
|---|---|---|
| Continuous Delivery | Performance trigger | Delivery of increments obligates immediate payment—not project completion |
| Contingency Reserve | Risk response resource | Time/money for known risks with active strategies; part of cost baseline |
| Threat vs Opportunity | Risk classification | Threat = negative effect; Opportunity = positive effect on objectives |
| Time and Materials Contract | Contract type example | Hybrid of cost-reimbursable and fixed-price; tested for classification |
Quick Review Questions
-
A seller delivers a feature increment to the customer using automation technology. When does the performance obligation for payment arise?
-
Your project uses a T&M contract. The seller submits an invoice for materials at cost plus labor at a fixed hourly rate. Is this correct under PMBOK v8 definitions?
-
During procurement monitoring, you identify a discrepancy in deliverables. What is the PMBOK v8 recommended action?
-
A risk is identified that could negatively affect project objectives. Is this a threat or an opportunity?
-
Your cost baseline includes a reserve for known risks with active response strategies. Is this contingency reserve or management reserve?
PMBOK v8 Reference
Section 3.5 - Glossary: "continuous delivery," "contract," "contingency reserve," "threat," "time and materials (T&M) contract"
Section 3.4 - Procurement Management: seller selection criteria, contract negotiation, monitoring and controlling procurements