Agile Contracting on the PMP Exam: Fixed-Price, T&M, and Target-Cost Explained

Published: 2026-05-27 · By FreePMPTests Editorial Team

Procurement questions on the PMP exam have always been challenging. Add agile to the mix, and they can feel downright contradictory. How do you sign a contract for a project when you don't know exactly what you're building? How does a Product Owner manage vendor relationships in an iterative delivery model? And what does PMI actually recommend when procurement meets agile?

This article will give you a clear, exam-ready understanding of how contracting works in agile and hybrid projects. We'll cover the contract types PMI expects you to know, how agile changes the procurement game, and the specific patterns the exam uses to test this knowledge.

The Core Tension: Predictability vs Flexibility

At its heart, the conflict between traditional contracting and agile delivery comes down to a simple tension. Traditional procurement assumes you know what you're buying before you sign the contract. You define a detailed Statement of Work (SOW), specify deliverables, and agree on a price. Agile assumes you'll discover what you need as you go — responding to feedback, reprioritizing the backlog, and adapting to change. Trying to nail down a detailed SOW at the start of an agile project is like trying to write a restaurant review before you've seen the menu.

PMI recognizes this tension and addresses it explicitly in the PMBOK Guide Seventh Edition and the Agile Practice Guide. The exam tests whether you can match the right contract type to the right project context — and whether you understand the risks and trade-offs of each.

Contract Types You Must Know for the PMP Exam

There are three major contract categories PMI expects you to know, and each has different implications for agile projects. Let's walk through them from the perspective of the buyer (your organization).

Fixed-Price Contracts (Firm-Fixed-Price, FFP)

In a fixed-price contract, the seller agrees to deliver a defined scope for a set price. The risk of cost overruns sits almost entirely with the seller. For the buyer, this sounds ideal — you know exactly what you're paying. But there's a catch: fixed-price contracts require a detailed, stable scope upfront. If the scope changes (and in agile, scope is expected to evolve), you'll need a formal change order — which adds cost, time, and friction.

When fixed-price works for agile: Almost never for the entire project. However, fixed-price contracts can work for individual sprints or for a well-defined increment when the team has already completed enough discovery to estimate confidently. Some organizations use a hybrid approach: a fixed-price contract for the first few sprints (discovery and MVP), with a renegotiation point before continuing.

Exam warning: If a question describes an agile project with evolving requirements and one of the answer options is "use a firm-fixed-price contract," that answer is almost certainly wrong. Fixed-price contracts lock scope — and agile requires scope flexibility.

Time and Materials Contracts (T&M)

T&M contracts pay the seller for the time spent and materials used. The buyer assumes the cost risk, but gains maximum flexibility to change direction, reprioritize, and adapt. This makes T&M the most natural fit for pure agile projects. You're essentially buying a team's capacity for a period of time, not a specific set of deliverables. The Product Owner controls what the team works on via the backlog; the contract simply says "this team works for us for the next six sprints."

When T&M works for agile: Nearly always. T&M aligns perfectly with the agile principles of iterative delivery, evolving scope, and customer collaboration. The buyer can adjust the backlog every sprint, and the seller gets paid for the work actually performed.

Exam warning: PMI expects you to recognize T&M as the preferred contract type for agile projects. However, PMI also wants you to acknowledge the buyer's risk. A T&M contract without a not-to-exceed cap or clear governance structure can lead to runaway costs. The exam may present scenarios where you need to recommend adding controls to a T&M contract without switching to fixed-price.

Target-Cost Contracts (Cost-Plus-Incentive-Fee, CPIF)

Target-cost contracts set a target cost for the work, and the buyer and seller share any cost savings or overruns according to a pre-agreed formula. This creates an incentive for the seller to control costs while preserving some flexibility for the buyer. Target-cost contracts can be adapted for agile projects through the use of incremental targets and regular review points.

When target-cost works for agile: In larger enterprise agile engagements where the buyer wants cost predictability but the seller needs protection against scope that could evolve significantly. The target can be set for a release or a program increment rather than the entire project, and adjusted at each planning interval.

Exam warning: PMI views target-cost contracts as a viable compromise for agile projects at scale. They're not as common on the exam as T&M, but you should recognize them as a legitimate option, especially in questions about large agile programs involving external vendors.

Agile-Specific Contract Models

Beyond the traditional contract types, PMI recognizes several agile-specific contracting approaches. While you don't need to memorize every detail, you should know they exist and understand the principles they embody:

• Graduated Fixed-Price: The contract has a fixed-price ceiling, but the buyer only pays for work actually delivered and accepted. If the seller finishes early or under budget, the buyer pays less. This incentivizes early delivery and discourages gold-plating.
• Money for Nothing, Change for Free: The buyer can terminate the contract early if the product is good enough, paying the seller a portion of the remaining budget. The seller, in return, accepts scope changes within the original vision at no additional cost. This aligns both parties around value delivery rather than scope completion.
• Incremental Delivery Contracts: The contract is structured as a series of delivery increments, with payment tied to the acceptance of each increment. The buyer can choose to continue or stop after each increment — giving them regular off-ramps.

How Agile Changes Procurement: Key Shifts for the PMP Exam

PMI identifies several fundamental ways agile transforms the procurement process. These are high-yield concepts for the exam:

1. From "Buying Deliverables" to "Buying Capacity"

In traditional procurement, you buy a deliverable — a software system, a bridge design, a training program. In agile procurement, you're often buying a team's capacity to solve problems iteratively. The contract specifies the team composition, the sprint cadence, and the governance model, not the detailed feature list. The exam rewards recognizing this mindset shift.

2. From "Big Requirements Upfront" to "Evolving Backlog"

Traditional RFPs include hundreds of pages of requirements. Agile procurement focuses on the product vision, the team's capabilities, and the collaboration model. The detailed requirements emerge through the backlog refinement process. PMI exam questions may ask what should be included in an RFP for an agile project — the correct answer emphasizes vision, team qualifications, and delivery approach over exhaustive requirements.

3. From "Arms-Length Vendor" to "Collaborative Partnership"

Agile contracts work best when the vendor team is treated as a partner, not an adversary. Daily standups include vendor team members. The Product Owner works directly with the vendor's developers. Retrospectives include both buyer and seller participants. PMI strongly endorses this collaborative approach, and the exam reflects it. Answers that pit buyer against seller (withholding payment, escalating contractually) are rarely correct.

4. From "Sign-Off at the End" to "Continuous Acceptance"

In traditional procurement, the buyer inspects and accepts the deliverable at the end. In agile, acceptance happens every sprint — the Product Owner reviews the increment and either accepts it or provides feedback. This dramatically reduces the risk of delivering something the buyer doesn't want. The exam tests this via scenarios about acceptance criteria and Definition of Done in vendor relationships.

When Traditional Contracts Work for Agile Projects

Despite everything we've said about T&M being the natural fit, PMI recognizes that organizations often must use traditional contract vehicles — especially in government, regulated industries, and large enterprises with established procurement policies. The question isn't whether traditional contracts are ideal for agile, but how you can adapt them to preserve agile benefits.

Here's PMI's guidance for making traditional contracts work in agile environments:

• Use a modular SOW. Instead of one massive Statement of Work, break it into smaller statements aligned to releases or program increments. Each module can be adjusted based on what was learned in the previous one.
• Build in regular review points. Even a fixed-price contract can include scheduled reviews where the buyer and seller discuss backlog adjustments within the agreed scope envelope.
• Define scope as outcomes, not features. Instead of specifying 47 individual features, define the business outcomes the project should achieve. This gives the team flexibility in how they deliver value.
• Include a change management mechanism designed for agile. Traditional change control boards move too slowly for agile cadences. Consider a lightweight change process where the Product Owner and vendor representative can approve backlog changes within a pre-authorized scope envelope.
• Structure payment on delivered value, not milestone documentation. Pay the vendor when working software is demonstrated and accepted, not when design documents are signed off.

PMP Exam Patterns for Procurement Questions

When the PMP exam tests procurement in an agile or hybrid context, watch for these recurring patterns:

Pattern 1: The Contract-Type Selection Question

"An organization is initiating an agile software development project with an external vendor. The requirements are expected to evolve significantly based on user feedback. Which contract type should the project manager recommend?" The correct answer is T&M (or an agile-specific variant). Fixed-price is wrong because evolving requirements would trigger endless change orders.

Pattern 2: The Vendor Collaboration Question

"A vendor team working under a T&M contract has fallen behind on their sprint commitment for the third consecutive sprint. What should the project manager do?" The correct answer involves collaboration: meet with the vendor to understand the root cause, inspect their processes, and work together on improvement — not "invoke the penalty clause" or "terminate the contract." PMI always prefers collaboration over escalation.

Pattern 3: The Agile Procurement Setup Question

"An organization transitioning to agile wants to procure a development team for a new product. What should be included in the RFP?" The correct answer emphasizes the product vision, team qualifications, collaborative expectations, and delivery cadence. Answers focused on exhaustive functional specifications are wrong.

Pattern 4: The Hybrid Procurement Question

"A large infrastructure project (predictive) includes a software component being developed with Scrum by an external vendor. How should procurement be structured?" The correct answer recognizes that different workstreams need different contract approaches. The infrastructure work may use a fixed-price contract while the software work uses T&M — and the project manager's job is to coordinate both.

Procurement on the PMP exam rewards nuanced thinking. You can't just memorize "agile = T&M" and call it a day. You need to understand the trade-offs, the adaptation strategies, and PMI's strong preference for collaboration over contractual combat. Master these principles, and you'll handle agile procurement questions with the same confidence as any other domain.