How to Rationalize and Transform Application Portfolios

Managing the application life-cycle isn’t just about cost savings.

A successful transformation process will focus on improving or developing new applications and business processes.

Architects also need to understand how applications depend on technology and infrastructure, and how they support business capabilities which impact customer and stakeholder satisfaction.

Start by identifying:

Who needs to be involved?
How you’ll keep them informed?
Goals and success metrics.

Who Are Your Stakeholders?

Identify who is Responsible, Accountable, Consulted and Informed for application portfolios.

This can guide the permissions you set up in your dashboards or reports. Common stakeholder groups include:

IT & Asset Managers

CIOs

Project Managers

Solution Architects

Dept. Heads/ Leads

Centralize Data in an Application Inventory

Good out-of-the box data integrations and an open API can do a lot of the heavy-lifting of data centralization. Top tips for managing data include:

Roundtripping data with Excel or Google Sheets can be a great way to get started
Mapping to services such as Technopedia and ServiceNow can keep details on vendors, versioning, and life-cycles updated. These can be set up so they’re either self-service or automated-delivery, depending on your preference.
Mapping to SharePoint lists will allow you to harvest content and keep it up to date.
Shadow IT is increasing, so assume that applications which aren’t on official registers exist. Walk the floors to understand who is using what, and where.

“Enterprises have up to 1000 cloud apps,
but CIOs think it’s just 30-40”

– Symantec

A Collaboration Hub Keeps Stakeholders Informed

A current and connected data set is key to successful application management. Data-owners need to access their application lists and reports. Managers and architects also need to capture information flows, business process and capabilities and technology infrastructure. They need to be able to edit this data easily day-to-day, updating the central repository.

Application portfolio lists, visualizations and reports should be easy to find. Ideally, they are online software embedded as part of the everyday workplace applications (MS Teams, or similar)

Accurate Metrics for Reporting on your Application Portfolio

Set up diagnostics to track the health of the application portfolio against your chosen success metrics (cost, reliability, risks). Pre-built algorithms in ABACUS are available to assist with these performance assessments. You can also set up predictive analytics to forecast metrics into the future.

To save time and effort, we recommend setting up analytics so they can be re-calculated automatically, updating throughout the portfolio. Algorithms can be used to calculate standard scores and indicators including:

ABACUS Visual Algorithm Composer Graphic Representation Demonstrating the ease of drag-and-drop algorithms

Cost & TCO
Business Fit & Technical Fit, including:
Reliability (Probability of a component failing)
Complexity (number of connections to technical elements such as servers, platform services, infrastructure services, databases)
Availability (proportion of time for which it is available, factoring in recovery time)

Cost calculations are particularly important, and should be set up to include both fixed and variable CapEx and OpEx costs and also indirect costs such as Server costs. By building up a cost profile of each application, you will then be able to assess the entire portfolio.

Best Application Portfolio Visualizations & Roadmaps

Schedule time regularly with Heads of Departments and the CIO to make sure they’re familiar with the application portfolio.

Start your presentations with simple charts showing how application transformation is both saving the business money, and improving metrics such as customer satisfaction. By setting up interactive charts and dashboards, you’ll also be able to drill-down into the repository to answer more detailed questions as you go.