Comprehensive Software Reviews to make better IT decisions
Map Your App! How the Application Portfolio Management Module Links EA Software to ALM Roles
Application portfolio management (APM) is typically characterized as a subset of application lifecycle management (ALM). However, in the software market (and in SoftwareReviews’ categorization) we typically see APM – not to be confused with application performance management or monitoring – included in enterprise architecture tools rather than in ALM software. The reason for this is that activities performed in APM rely more on the core competencies of enterprise architects than of those who partake in software development.
Activities of APM
Application portfolio management, in short, is a process of creating a clear picture of the current landscape and future strategy of an organization’s applications to better support business and technology decision making. APM consists of three principle components:
- Discovery: Investigating your software users and technology stack to produce up-to-date and detailed inventories capturing various application attributes and their alignment to other architectural components.
- Rationalization: Routinely assessing your application’s value, fit, cost, and performance to determine whether it is best to maintain, enhance, or retire.
- Roadmapping: Projecting and displaying any strategic disposition assigned to an application over a given timeline.
APM at its core is keeping application information accurate and providing thoughtful recommendations to the technology decision makers of your organization.
How Does Application Portfolio Management Fit Into ALM?
A simplified view of ALM breaks the topic down into three main aspects: development, operations, and governance. Development encapsulates the initial creation and subsequent new versions or continuous improvements of an application. Operations speaks to the work required to monitor and maintain an application from its initial deployment onwards. Various different software delivery approaches blend the responsibilities of development and operations, such as the aptly named DevOps.
Governance, in the context of ALM, can be broken down even further. Initial governance, commonly stated as business case development and project portfolio management, covers early lifecycle activities, from ideation and approval to development and implementation. Ongoing governance past implementation is where you find APM, which ensures the application continues to meet organizational needs and deliver value, while also managing its cost and risk to the organization. In this sense, APM acts as the business case and initial project planning functions for enhancements to applications already in operations.
Source: Chappell, 2014
When we look to APM in ALM software, it is not overly common to see these capabilities. Most ALM tools focus exclusively on development and operations, and only the more comprehensive solutions include APM – or any of the governance elements, for that matter.
How Does Application Portfolio Management Fit Into Enterprise Architecture?
As mentioned above, fit, or application-to-business capability alignment, plays a large role in APM. Understanding business capabilities and how those capabilities are delivered by different technology is a key component to discovery, and specifically to defining the features and functions of your applications (some of which are often unknown to IT). Moreover, it allows you to determine your redundancies and gaps, which is a necessary input to effective rationalization of the portfolio and determination of strategic dispositions.
The ability to clearly articulate and display the alignment between applications and business capabilities is a critical function of APM. However, that function relies on features that are inherent to an architect’s toolset. This is why EA tools are more likely to position themselves as the use case for APM.
Info-Tech’s recommendation is that the most productive application portfolio managers are those that have integrated ALM and architecture toolsets. Very few IT disciplines live in isolation. Bridging the gap between roles and subject matter expertise is key to effective IT organizations, as is connecting explicit information sources.
Want to Know More?
- Bridge IT and the Business With Business Architecture: Build a business architecture practice to lay the groundwork for APM.
- Visualize Your Application Portfolio Strategy With a Business-Driven Approach: Mature your APM practice with application rationalization.
- Build a Product Roadmap: Review approaches to showcasing your application’s strategy.
- Enhance Your Application Architecture: Understand how to model the full technology stack.
- Discover Your Applications: Learn how to extend business architecture to fully understand your apps and build an APM practice.
- Define an EA Operating Model: Standardize your modeling capabilities.
- Modernize your SDLC: View the dominant activities of ALM by analyzing your SDLC.
Dynatrace has filed for an IPO. IT professionals making APM purchasing decisions may benefit from the increased transparency when Dynatrace goes public.
Intake and backlog management are two of the top reasons for failed product and feature delivery. Skop.es brings the analytical and management practices to visualize, quantify, and verify and validate the delivery of the right requirements.
Application performance management (APM) is hard, but necessary. The vendor space is expanding because it addresses a real need.
Atlassian’s Jira remains a popular collaboration tool for teams looking to improve work coordination. However, it requires third-party add-ons and integrations to support end-to-end artifact traceability and product delivery. Zephyr fills Jira’s test management capability gap.
The immense sprawl of products and product versions across the organization complicates manual inventory collection practices. Automated discovery and inventory tools help alleviate this challenge, but they do not negate the importance of end user and stakeholder collaboration and application capability mapping.
Use your application lifecycle management (ALM) tools to manage the complexity of today’s frequent deployment cycles and ensure alignment and traceability with business objectives.
Teams want an open and integrated application lifecycle management (ALM) environment. Teams are now empowered to adopt the tools they need to address complexities and frequent changes while ensuring end-to-end artifact traceability. ALM integration hubs provide out-of-the-box connections when product delivery tools do not.
Stakeholders expect the speed and responsiveness of product delivery does not come at the expense of quality. QA tools offer retailers the ability to continuously ensure both business and technical quality standards are upheld, but these tools should not be viewed as a silver bullet.
While the Agile Manifesto might value individuals and interactions over processes and tools, modern product delivery SDLCs are automated. Unfortunately, there are a lot of tools and vendors creating confusion as they compete for a share of your wallet.