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?

  1. A signed contract from the customer
  2. The stakeholder register
  3. The risk register
  4. 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.

AI Systems with Claude, for Scrum Masters and Project Managers

Most AI pilots in project management do not fail on the model. They fail because somebody pointed the thing at a decision instead of at a task. This course is built around that distinction, and around the work that follows once you get it right.

Eight teaching sections, taught against one running project from the first lecture to the last. You watch a system get built, then you build the same one against your own sprint. Nothing here is a demo that works only on the example.

You finish with five working systems and you keep them. The sprint report machine turns your board export and standup notes into the report you currently write by hand. The retro intelligence system tells you what the team keeps saying, not just what it said this time. The stakeholder comms engine drafts the update in the register the audience expects. The backlog health monitor flags the quiet decay nobody has time to check for. The risk and dependency tracker follows the chains that actually bite.

Seventy-six working files ship with it, across four sections, so every system is built against real sprint data rather than material invented for a slide. Four sprints of retrospectives, board exports, standup notes, backlog and risk data.

Explore the Course


Lead with clarity, influence, and outcomes.

HK School of Management and Technology offers a practical Leadership for Project Managers course for real projects, tight deadlines, and cross-functional teams. Learn to set direction, align stakeholders, and drive commitment without relying on title. Practical skills, tools, and guidance you can apply right away. Covered by Udemy's 30-day refund policy.

Learn More