
Agreements in Project Management: Definition, Types, and Exam Relevance
PMBOK v8 Definition
Agreements are any document or communication that defines the initial intentions of a project. These agreements can take the form of a contract, service-level agreement (SLA), memorandum of understanding (MOU), letters of agreement, verbal agreement, purchase order, email, or other formal or informal communications. Agreements should comply with local, national, and international laws regarding contracts, and include a sufficiently detailed scope of work description so project team members understand what work is to be performed. Agreements can be simple or complex; a complex project may involve multiple contracts simultaneously or in sequence.
Note: Agreements are an output of the Plan Procurement Management process and an input to multiple processes across Project Procurement Management.
Why It Matters for the Exam
The PMI exam frequently tests your ability to identify what constitutes a valid agreement, distinguish between different types of agreements, and recognize when agreements are required as inputs or outputs. Questions often appear in the Procurement Management knowledge area and in stakeholder engagement scenarios where the initial intentions of a project must be formally documented. Expect situational questions where you must select the correct agreement type for a given project context.
Key Points to Remember (for the exam)
- Definition: Agreements are any document or communication that defines the initial intentions of a project—not just formal contracts.
- Common Forms: Contract, SLA, MOU, letters of agreement, verbal agreement, purchase order, email.
- Essential Content: Must include a unique identifier and a sufficiently detailed scope of work description so team members understand what work is to be performed.
- Legal Compliance: Agreements must comply with local, national, and international laws regarding contracts.
- Complexity: Can be simple or complex; complex projects may involve multiple contracts simultaneously or in sequence.
- Team Agreements (Distinct): Team agreements are a separate concept—they represent behavioral parameters and working norms established by the project team, not procurement agreements.
- Procurement Negotiation: Concludes with a signed contract document or other formal agreement that can be executed by both buyer and seller.
Typical PMI Exam Example
Scenario: A project manager is initiating a new software development project with an external vendor. The vendor sends an email outlining the project scope, delivery timeline, and payment terms. The project manager needs to confirm that this document qualifies as a project agreement.
Question: What should the project manager verify to ensure this email qualifies as a valid agreement under PMBOK v8?
Answer: The email must include a unique identifier and a sufficiently detailed scope of work description so team members understand what work is to be performed. Additionally, it must comply with applicable contract laws.
PMI Exam Traps
-
Trap: Thinking only formal contracts are agreements.
- Reality: Agreements include verbal agreements, emails, purchase orders, and MOUs—any communication defining initial intentions.
-
Trap: Confusing team agreements with procurement agreements.
- Reality: Team agreements are behavioral norms set by the project team; procurement agreements are about goods/services and legal obligations.
-
Trap: Assuming a single agreement is sufficient for complex projects.
- Reality: Complex projects may involve multiple contracts simultaneously or in sequence.
-
Trap: Overlooking legal compliance requirements.
- Reality: All agreements must comply with local, national, and international laws—not just formal contracts.
Important PMI Connections
| Related Concept | Relationship Type | Exam Attention Point |
|---|---|---|
| Approved Change Requests | Input to Procurement Processes | Approved changes may modify existing agreements; must be documented |
| Procurement Negotiation | Precedes Agreement Signing | Negotiation concludes with a signed contract or formal agreement |
| Integrated Project Delivery (IPD) Contracts | Specialized Agreement Type | Multiparty agreements with shared risks and rewards; used in complex construction |
| Team Agreements | Separate Concept (Behavioral) | Do not confuse with procurement agreements; team agreements are about working norms |
| Procurement Phases | Lifecycle Context | Agreements may span multiple phases; complex projects may sequence multiple contracts |
Quick Review Questions
-
What are the minimum required elements that every agreement must contain according to PMBOK v8?
-
List at least five different forms an agreement can take (beyond formal contracts).
-
What is the key difference between a procurement agreement and a team agreement?
-
In what situation would a project involve multiple contracts simultaneously or in sequence?
-
What must occur before a signed contract document or formal agreement can be executed by both buyer and seller?
PMBOK v8 Reference
Section X4.2 – Procurement Overview
(Also referenced in the context of Agreements as an output of Plan Procurement Management and as inputs to Conduct Procurements and Control Procurements)