Agreements
Any written or verbal record that sets out the early intent, expectations, or commitments for a project—such as a contract, memorandum of understanding (MOU), letter of agreement, email confirmation, or similar communication.
Key Points
- May be legally binding (e.g., contracts) or non-binding (e.g., MOUs, emails), but both guide project initiation.
- Common input to developing the project charter by clarifying high-level scope, objectives, and constraints.
- Should capture major deliverables, roles, acceptance or success criteria, assumptions, and boundaries at a high level.
- Must be documented, stored, and managed; updates follow change control or contract management processes.
Example
A client signs an MOU and sends an email confirming budget limits and desired outcomes for a new software rollout. These communications serve as the agreement that informs the project charter and initial planning.
PMP Example Question
Before drafting the project charter, which artifact would qualify as an Agreement and serve as an input to initiation?
- A signed contract from the customer
- The stakeholder register
- The risk register
- The work breakdown structure (WBS)
Correct Answer: A — A signed contract
Explanation: Agreements include items like contracts, MOUs, and emails that capture early commitments and are inputs to developing the project charter. The other documents are typically created later in planning.