Portfolio Backlog Item Data Object

Purpose

The Portfolio Backlog Item data object is a discrete and specific statement of work with acceptance criteria, funding requirements, and detailed work definitions. It may be a collection of many smaller work items, such as work packages or Product Backlog Items.

Key Attributes

The Portfolio Backlog Item data object shall have the following key data attributes:

  • Id: unique identifier; e.g., number of the Portfolio Backlog Item

  • Name: descriptive title of what the Portfolio Backlog Item represents

  • Description: short description of the work contained within the Portfolio Backlog Item

  • Prioritization: current priority on the Portfolio Backlog

  • Acceptance Criteria: what must be accomplished by the work in order to consider the item complete and accepted

  • Related Products: products that are impacted by the execution and completion of this work

  • Demand Profile: detailed list of how this Portfolio Backlog Item will consume resources such as labor, contracts, infrastructure, etc.

  • Cost Estimation: estimated cost derived from the demand profile

Key Data Object Relationships

The Portfolio Backlog Item data object shall maintain the following relationships:

  • Portfolio Backlog Item to Strategic Objective (n:m): a strategic initiative may drive the creation and prioritization of many Portfolio Backlog Items; the Portfolio Backlog Item may satisfy the objectives of many strategic initiatives

  • Portfolio Backlog Item to Architecture Roadmap Item (n:1): a Portfolio Backlog Item must align to the authoritative Architecture Roadmap Item

  • Portfolio Backlog Item to Policy (n:m): Portfolio Backlog Items may be sourced from Policies or may reference Policies to demonstrate compliance

  • Portfolio Backlog Item to Scope Agreement (1:1): a Portfolio Backlog Item can have one corresponding Scope Agreement

  • Portfolio Backlog Item to Digital Product (n:m): a Portfolio Backlog Item may be executed or impact many Digital Products; a Digital Product may be executing work against many Portfolio Backlog Items

  • Portfolio Backlog Item to Product Backlog Item (1:m): Portfolio Backlog Items may contain many Product Backlog Items; a Product Backlog Item is related to one Portfolio Backlog Item

  • Requirement to Portfolio Backlog Item (n:m): Requirements can be associated with one or more Portfolio Backlog Items