Application Portfolio Management (APM) Best Practices

Overview

Some of the most operationally grounding APM data - defect rates, incident frequency and severity, change volume, performance metrics - is generated and maintained by operational teams that are not part of the APM function and should not be asked to relinquish ownership of it. QA teams own defect records as a core operational tool. IT Operations owns incident records. Change Management owns change records. Monitoring owns performance data. This data is gold for portfolio analysis - an application with a high defect rate and frequent incidents is a visible candidate for investment or retirement regardless of its technical fitness assessment score - but it belongs operationally and must be consumed, not acquired.

Best Practice

Establish formal data-sharing arrangements with the operational teams that own operationally-homed inventories relevant to APM analysis. Define what data APM needs from each operational source, at what frequency, in what format, and with what quality standards. Consume this data as an authorized downstream consumer under a formal agreement, not as an owner acquiring control of data that belongs elsewhere. Do not replicate or duplicate the operational data stores - establish agreed-upon access mechanisms that allow APM to query operational data in place or receive regular governed exports. Use AI to analyze and integrate operational data with portfolio data in a common analysis environment without requiring complex data integration pipelines.

Benefit(s)

Consuming operationally-homed data through formal sharing arrangements enriches the portfolio view with operational ground-truth that static inventory data alone cannot provide. Operational signals - high defect rates, recurring incidents, excessive change volume, degrading performance trends - become visible portfolio analytics that inform rationalization decisions, investment priorities, and risk assessments. The portfolio view gains operational credibility that resonates with operational leaders who may otherwise be skeptical that APM understands the operational realities of the applications it governs.