Purpose:

Ensure that the supplier and the acquirer perform according to the terms of the supplier agreement.

Objective:

Establishes organizational expectations to manage the supplier agreement by performing the acquirer activities defined in the supplier agreement, monitoring selected supplier processes, accepting the product or service, and managing supplier invoices.

Description:

Agreement Management addresses the delivery of the acquisition of products and services to the project’s customer or included in a product or service system. Solicitation and Supplier Agreement Development addresses the acquisition of products and services.

Where the terms “product” and “product component” are used, their intended meanings also encompass services, service systems, and their components.

To minimize risks to the project, Agreement Management can also address the delivery of the acquisition of significant products and product components not delivered to the project’s customer but used to develop and maintain the product or service (for example, development tools and test environments).

Typically, the products to be acquired by the project are determined during the early stages of planning and development.

The Acquisition Technical Management determines the products and product components that need to be acquired from suppliers.

Agreement Management does not directly address arrangements in which the supplier is integrated into the project team and uses the same processes and reports to the same management as the project team members (e.g., integrated teams). Typically, these situations are handled by other processes or functions (e.g., project management processes, processes or
functions external to the project) though some of the specific practices of these processes can be useful in managing the supplier agreement.

Agreement management typically is not implemented to address arrangements in which the project’s customer is also a supplier. These situations are usually handled by either informal agreements with the customer or by the specification of the customer-furnished items in the overall agreement that the project has with the customer. In the latter case, some of the specific practices of this process area can be useful in managing the agreement, although others may not, due to the fundamentally different relationship that exists with a customer as opposed to an ordinary supplier.

RASIC:

Agreement Management

Entrance Criteria:

  • <?>

Exit Criteria:

  • <?>

Process and Procedures:

Tailoring Guidelines:

  • PM to VMO

Process Verification Record(s)

  • Integrated list of issues
    • Stored By: Project Manager
  • Acquisition of project progress and performance reports
    • Stored By: Project Manager
  • Supplier review materials and reports
    • Stored By: Project Manager
  • Action items tracked to closure
    • Stored By: Project Manager
  • Records of product and document deliveries
    • Stored By: Project Manager
  • List of processes selected for monitoring or rationale for non-selection
    • Stored By: Project Manager
  • Activity reports
    • Stored By: Project Manager
  • Process performance reports
    • Stored By: Project Manager
  • Process performance curves
    • Stored By: Project Manager
  • Discrepancy reports
    • Stored By: Project Manager
  • Stakeholder Approval Reports
    • Stored By: Project Manager
  • Discrepancy Reports
    • Stored By: Project Manager
  • Product Acceptance Review Report with Approval Signatures
    • Stored By: Project Manager
  • Invoices Approved for Payment
    • Stored By: Project Manager

Supplier Deliverables

    • Supplier project progress and performance reports
      • Stored By: <?>
    • Corrective action results for supplier issues
      • Stored By: <?>
    • Correspondence with the acquirer
      • Stored By: <?>
    • Supplier Process Quality Assurance Reports
      • Stored By: <?>
    • Work Products as Defined in the Supplier Agreement
      • Stored By: <?>
    • Services as Defined in the Supplier Agreement
      • Stored By: <?>
    • Invoices
      • Stored By: <?>

Measure(s):

  • <?>
    • Maintained By: <?>
    • Submitted By: <?>
    • Frequency of Submission: <?>

References:

  • CMMI® for Development, Version 1.3, Software Engineering Process Management Program, November 2010
  • CMMI® for Acquisition, Version 1.3, Software Engineering Process Management Program, November 2010
  • CMMI® for Services, Version 1.3, Software Engineering Process Management Program, November 2010