Application Portfolio Management (APM) Best Practices

Overview

Owning APM as a practice and owning the inventory data that APM depends on are two related but distinct ownership responsibilities. The APM practice must be owned by a function with enterprise scope and a clear leadership mandate. The inventory data that feeds APM exists across multiple sources with different owners - some centrally owned because they have no natural operational home, and some operationally owned by the teams that generate and maintain them. Understanding and designing this ownership landscape is foundational to APM success and is one of the most commonly mishandled aspects of APM program design.

Best Practice

Assign explicit ownership of the APM practice to the designated enterprise-spanning function, operating on behalf of and with the authority of IT leadership. Separately, establish clear ownership of the inventory data that APM depends on. Enterprise Architecture and Engineering should own the cross-enterprise inventories that have no natural operational home - the Applications Inventory, Software Licenses Inventory, Software Subscriptions Inventory, Data Integrations Inventory, Vendors and Suppliers Inventory, and similar inventories that span organizational boundaries. Operationally-homed inventories - defect records from QA, incident records from IT Operations, change records from Change Management - should remain with their operational owners. APM is a consumer of operationally-homed data, not its owner. Make this distinction explicit in the APM Governance Policy.

Benefit(s)

Distinguishing practice ownership from data ownership produces an APM capability that is both authoritative and efficient. The APM practice has clear organizational standing and leadership mandate. The inventory data it depends on is owned by the teams with the deepest knowledge of it. Operationally-homed data remains with its operational owners, who maintain it as part of their existing responsibilities rather than as an additional burden imposed by a central team. APM consumes all of this data as an integrator and intelligence layer, not as an acquirer trying to own everything it touches.