Digital Product Data Object


A Digital Product data object is an entity representing the Digital Product throughout its entire lifecycle. It is used to organize activities across all value streams.

A more elaborate description of Digital Product is provided in the Digital Product chapter, to include types of Digital Products, examples, and rationale for definitions as supported by this data object.

Key Attributes

  • Id: unique product identifier

  • Name: descriptive, common name of the Digital Product

  • Description: short description of the Digital Product

  • Product Manager: name of the Digital Product Manager

  • Investment Status: status of the Digital Product; e.g., invest, divest, sustain, retired, etc.

  • Portfolio: portfolio to which the Digital Product belongs

  • Business Criticality: indication of the importance of the Digital Product for the business

  • Security Risk: indication of the business risk if the Digital Product is compromised

  • Budget: approved budget for ongoing resources, development, maintenance, and services

  • Total Cost of Ownership (TCO): the total cost of ownership of the Digital Product (includes all development, run, enhancement, and overhead charges for systems and shared costs)

  • Profit/Loss: calculated chargeback/showback against TCO for the Digital Product

Key Data Object Relationships

The Digital Product data object shall maintain the following relationships:

  • Digital Product to Policy (n:m): multiple Policies might be applicable for a single Digital Product or a single Policy may be applicable for multiple Digital Products

  • Digital Product to Value Stream (n:m): traceability is maintained between Digital Products and the Value Stream it supports

  • Digital Product to Portfolio Backlog Item (1:n): one Digital Product may be related to one or more Portfolio Backlog Items

  • Digital Product to Architecture Blueprint (n:m): traceability may be maintained between one or more Digital Products and the Architecture Blueprint drawings, diagrams, and other planning documents

  • Digital Product to Scope Agreement (n:m): Digital Products may have one or more Scope Agreements associated with them

  • Digital Product to Product Design (1:n): Digital Products will have one or more Product Designs associated with each version/model of the Digital Product

  • Digital Product to Digital Product (n:m): a Product can depend on services being delivered by other Products