Application Portfolio Management (APM) Best Practices - Distinguish between the active portfolio and the application pipeline
Application Portfolio Management (APM) Best Practices
Distinguish between the active portfolio and the application pipeline
Overview
Applications under development, in evaluation, or in pilot are not yet Active applications. They have not been validated against production requirements, have not completed governance review required for Active status, and may change significantly or not proceed to Active status at all. When Proposed applications are listed alongside Active applications without clear distinction, the portfolio presents a misleading picture of current operational capability. Decision-makers may assess the portfolio’s capability coverage based on planned rather than actual capability, leading to investment decisions that duplicate what is already in progress.
Best Practice
Maintain a strict, visible boundary between the Active portfolio and the application pipeline in all portfolio reporting, communication, and governance documentation. The Active portfolio contains only applications fully deployed, validated, and available to their intended users under the governance of the lifecycle model. The application pipeline is reported separately, with explicit labeling indicating it represents planned and in-progress capability rather than current operational capability. Never represent pipeline applications as portfolio applications in capability maps, service catalogs, or operational planning documents without clearly indicating their development or evaluation status and the governance conditions required for Active status.
Benefit(s)
A strict Active-pipeline boundary preserves the accuracy and trustworthiness of the portfolio as a representation of current organizational capability. Users and business leaders can rely on the Active portfolio as an accurate representation of what is currently available for operational use. Pipeline reporting informs future planning without inflating the current capability picture or creating premature expectations. The organization develops portfolio communication practices that build stakeholder trust in the accuracy and reliability of portfolio data.
Copyright for the International Foundation for Information Technology (IF4IT): 2008 - Present
Legal Disclaimers