Scope Agreement Data Object

Purpose

The Scope Agreement data object represents a proposal to implement one or more rationalized Portfolio Backlog Items and Budget Items. Scope Agreements reflect budget, cost/benefit projections, scope, status, and other key attributes of proposed work. They can be defined in the context of portfolio- or product-level concerns. The Scope Agreement represents the agreement between the requesting party (usually the Digital Product portfolio manager) and the delivery party (such as a Digital Product delivery team) on the work to be performed to implement the specified Portfolio Backlog Items and the funding available for the implementation.

Key Attributes

The Scope Agreement data object shall have the following key data attributes:

  • Id: unique identifier of the Scope Agreement

  • Description: details of the Scope Agreement

  • Business Entity: business or geographic unit

  • Anticipated Business Value (optional): projected business value, over a given time period, anticipated once the corresponding products and capability have been delivered

  • Proposed Budget: requested budget of the Scope Agreement; this should be broken down into a build and a run budget

  • Approved Budget: approved budget of the Scope Agreement; this should be broken down into a build and a run budget

  • Status: Scope Agreement (e.g., created, proposed, approved, rejected, deferred)

  • Context: portfolio level, product level

Key Data Relationships

The Scope Agreement data object shall maintain the following relationships:

  • Scope Agreement to Portfolio Backlog Item (n:m): one Scope Agreement can be associated to one or more demand data objects

  • Scope Agreement to Budget Item (n:1): this relationship helps track the budget allocated to each Scope Agreement

  • Scope Agreement to Product Backlog Item (1:n): this relationship helps track Digital Product(s) to each Scope Agreement