Application Portfolio Management (APM) Best Practices - Maintain an application portfolio roadmap at the enterprise level
Application Portfolio Management (APM) Best Practices
Maintain an application portfolio roadmap at the enterprise level
Overview
Individual application teams maintain their own development and maintenance roadmaps, but these individual roadmaps do not aggregate into a coherent enterprise portfolio roadmap without deliberate effort to synthesize them. Without an enterprise-level portfolio roadmap, there is no aggregate picture of where the portfolio is going: which capabilities are being built, which applications are being retired, which modernization programs are underway, and how the portfolio will look in one, two, and three years. Strategic planning, resource allocation, and architectural direction are all constrained by the absence of this portfolio-level forward visibility.
Best Practice
Maintain an enterprise-level application portfolio roadmap that integrates the major portfolio changes planned over the next one to three years into a coherent, navigable view of portfolio evolution. The roadmap should capture: planned new applications entering the Active portfolio from the pipeline with their expected Active dates and business capability contributions; planned migrations, modernizations, and major investments in existing Active applications with their expected completion dates and outcomes; planned deprecations and retirements with their retirement dates and disposition approaches; major lifecycle transitions for significant applications; and the aggregate resource and investment profile implied by the planned changes. Review and update the roadmap quarterly and present it to leadership as a standard element of portfolio governance reporting.
Benefit(s)
An enterprise portfolio roadmap provides the forward visibility that strategic planning, resource allocation, and architectural direction require. Leaders can see where the portfolio is going and make investment decisions in the context of planned portfolio evolution rather than in isolation from it. Resource planning accounts for the engineering, operational, and financial demands of planned portfolio changes before those demands arrive rather than after they have already created organizational strain. The roadmap becomes the primary communication tool for portfolio strategy, making the APM program’s direction visible, understandable, and engaging to all organizational stakeholders.
Copyright for the International Foundation for Information Technology (IF4IT): 2008 - Present
Legal Disclaimers