Application portfolio management (APM) is a framework for managing enterprise IT software applications and software-based services. APM provides managers with an inventory of the company's software applications and metrics to illustrate the business benefits of each application.
Next Steps
-
APM Brochure
This resource details how, by leveraging modern...
(Bitpipe.com) -
APM processes: Determining apps’ business value
Application portfolio management aids decision ...
(SearchSoftwareQuality.com)
An APM system uses a scoring algorithm for generating reports about the value of each application and the health of the IT infrastructure as a whole. By gathering metrics like an application's age, how often it's used, the cost it takes to maintain it and its interrelationships with other applications, a manager can use more than just an educated guess to decide whether or not a particular application should be kept, updated, retired or replaced.
According to NASA's Office of the Chief Information Officer :
"[APM] is really about implementing a repeatable process to assess what we have, and, if an application is not performing or does not meet our architectural requirements, eliminating it and replacing it with a better performing application. We’re doing it to try and reduce the money we spend on maintaining existing applications (that don’t perform well) and freeing up that money to invest in new and better performing applications."
Learn more:
Wikipedia says the two main categories of Application Portfolio Management solutions are generally referred to as 'Top Down' and 'Bottom Up' approaches.
Mike Walker writes about the Integration of Enterprise Architecture and Application Portfolio Management for the Microsoft Developers Network website.
The NASA Office of the Chief Information Officer website provides more information about the importance of application portfolio management.
"[APM] is really about implementing a repeatable process to assess what we have, and, if an application is not performing or does not meet our architectural requirements, eliminating it and replacing it with a better performing application. We’re doing it to try and reduce the money we spend on maintaining existing applications (that don’t perform well) and freeing up that money to invest in new and better performing applications."
Tech TalkComment
Share
Comments
Results
Contribute to the conversation