Application Portfolio Management (APM) Best Practices - Build and maintain key mappings between applications and the people, processes, and data they depend on

Application Portfolio Management (APM) Best Practices

Chapter 32. Build and maintain key mappings between applications and the people, processes, and data they depend on

Executive Summary: Chapter Overview

IF4IT

The Bottom Line

Core Concepts

Quick Q&A

Question: What kinds of portfolio decisions require these dependency mappings?

Question: How does APM avoid becoming responsible for every dependency inventory?

Read More Below

How to cite this page

When referencing this page in academic work, internal standards, or external publications, include the page title, IF4IT as author and publisher (The International Foundation for Information Technology (IF4IT), LLC), the URL, and your access date.

Example (informal web citation):

The International Foundation for Information Technology (IF4IT), LLC. Build and maintain key mappings between applications and the people, processes, and data they depend on | Application Portfolio Management (APM) Best Practices. https://if4it.org/best-practices/application-portfolio-management-apm/build-and-maintain-key-mappings-between-applications-and-the-people-processes-and-data-they-depend-on/ (accessed 2026-07-20).

See About Us for content governance and site-wide citation guidance.

Copyright for The International Foundation for Information Technology (IF4IT), LLC: 2008 - Present

Legal Disclaimers