According to most industry perceptions, application performance management (APM) and application portfolio management (APM) might seem to be worlds apart — or at best connected by a very thin thread. Much of this, admittedly, comes from application portfolio planning's roots in project and portfolio management, which lived in another realm and in my view in another era — when a cloistered development team got most of its go-ahead information from often equally cloistered business analysts. In other words, when the fertile dialog that's emerging between development, operations and ITSM teams was still in its infancy.
In this blog, I'd like to highlight three areas that are bridging the APM-to-APM divide: digital experience management, application discovery and dependency mapping (ADDM), and agile/DevOps lifecycle planning.
Digital Experience Management
In my view, probably the single most important lane in our 3-lane bridge connecting the two APMs is digitalor user experience management. Coincidentally, this is a technology area where I've witnessed another set of colliding acronyms — user experience management (UEM) and unified endpoint management(UEM), which also have at least a plank to unite them.
EMA's recent research revealed a striking connection between digital experience management and application portfolio planning right out of the gate. When asked, "Over the past three years, what has become more important for digital experience management?" application portfolio planningtied with application performance managementfor first place! If you're curious, agile, business development and customer management and cloudcame next.
Why was this just waiting to happen? Our data suggests that the answer lies in the fact that digital experience management embraces not only application performance, but also application outcomes and relevance. For instance, when we asked, "When you talk about digital experience management, what do you see bringing you the most value?" the answers in ranked order were:
1. Business impact
3. Change management
Of these, business impact, design, productivityand usageall directly inform business RELEVANCE and VALUE. In other words, if you wanted to plan your application portfolio meaningfully, wouldn't you want to capitalize on these insights which are, by the way, dynamic, real-time, and can be trended to correlate with business performance overall?
But COST was also a factor. In fact, given the pressures on IT for transparency in the "age of cloud" cost has become increasingly central to IT executive planning. When we asked about business metrics applied to digital experience management, the top five were:
1. Cost-related external SLAs with cloud and other service providers and partners
2. Business activity management impacts
3. Revenue-related impacts
4. Business process impacts
5. Service desk operational efficiencies
What you see is a sandwich — with two pieces of bread focused on cost (one and five) and the middle section (lettuce, cheese and ham?) squarely focused on value. All of these are relevant sources for meaningful application portfolio planning and management.
Application Discovery and Dependency Mapping
ADDM is really a bridge to many things. As you know, it can be central in understanding, prioritizing and resolving performance issues associated with application services by capturing application-to-infrastructure, as well as application-to-application, interdependencies. It is also an area of vast innovation in the industry, tied to multiple use cases with multiple product architectures and designs.
Two of the more prominent use cases for ADDM are change management and asset management. The latter is particularly relevant here because it connects business services with actual costs. Costs in terms of public cloud investments, on-premise hardware and software, and potentially even operational costs associated with everything from infrastructure management to software audits. In other words, ADDM can provide inestimable value in mapping the end products of IT (its application/business services) to all the associated costs surrounding the creation, delivery and support of those products.
Of course to do this, more than ADDM is required. More advanced investments in IT service management (ITSM), IT governance analytics, and more fluid approaches to IT asset management (ITAM) and software asset management (SAM) are needed to color in the picture. Best of all, though, once again, all this data is real (not just surmised), dynamic and current, and can be trended over time to capture historical insights into the real costs of managing an application business service.
On the one hand, linking application portfolio management to agile and DevOps should be a no-brainer. Pretty easy to figure that associated planning needs to be done before speedy execution. But I'm highlighting the connection here because the current focus on agile is all about speed, not about relevance. The truth is, as I like to say, you can "automate train wrecks." You can also, frankly, be "agile and dumb" –speedily doing enhancements that don't bring the most value at the cost to others that are far more relevant to business outcomes. So, I'd like to suggest a new brand for "agile" called "Informed Agile" — where APM truly meets APM.
In wrapping up, I'd like to add that I didn't mean these three lanes in the bridge between the two APMs to be complete or the last word. I'm sure there are other areas where APM meets APM, beyond these three. The very nature digital transformation, and the closely associated role of IT transformation, could add any number of layers, from SecOps requirements to advance IT analytics.
It seems to me that the time has already arrived for IT to look beyond traditional ways of working. The idea notion that business experts sit on one side of a wall, and IT professionals sit on the other now seems to belong to the past. That wall is crumbling, and the opportunity to have common conversation with common data points is finally emerging.
Modern complex systems are easy to develop and deploy but extremely difficult to observe. Their IT Ops data gets very messy. If you have ever worked with modern Ops teams, you will know this. There are multiple issues with data, from collection to processing to storage to getting proper insights at the right time. I will try to group and simplify them as much as possible and suggest possible solutions to do it right ...
In Agile, development and testing work in tandem, with testing being performed at each stage of the software delivery lifecycle, also known as the SDLC. This combination of development and testing is known as "shifting left." Shift left is a software development testing practice intended to resolve any errors or performance bottlenecks as early in the software development lifecycle (SDLC) as possible ...
Overwhelmingly, business leaders cited digital preparedness as key to their ability to adapt, according to an in-depth study by the Economist Intelligence Unit (EIU), looking into how the relationship between technology, business and people evolved during the COVID-19 pandemic ...
Robotic Data Automation (RDA) is a new paradigm to help automate data integration and data preparation activities involved in dealing with machine data for Analytics and AI/Machine Learning applications. RDA is not just a framework, but also includes a set of technologies and product capabilities that help implement the data automation ...
There is no one-size-fits-all approach to changing the experience of employees during a pandemic, but technological innovation can have a positive impact on how employees work from home as companies design their digital workspace strategy. The IT team supporting this shift needs to think about the following questions ...
Downtime. It's more than just a bar on the Rebel Alliance's base on Folor. For IT Ops teams, downtime is not fun. It costs time, money and often, user frustration. It takes more than the Force to handle incidents ... it takes an intergalactic team. An effective incident management team is made up of people with many different skill sets, styles and approaches. We thought it would be fun to map the heroes of IT Ops with Star Wars characters (across Star Wars generations) based on their traits ...
Vendors and their visions often run ahead of the real-world pack — at least, the good ones do, because progress begins with vision. The downside of this rush to tomorrow is that IT practitioners can be left to ponder the practicality of technologies and wonder if their organization is ahead of the market curve or sliding behind in an invisible race that is always competitive ...
According to a new report, Digital Workspace Deployment & Performance Monitoring in the New Normal, 82% of respondents had changes in their digital workspaces due to the pandemic ...
There are a few best practices that DevOps teams should keep in mind to ensure they are not lost in the weeds when incorporating visibility and troubleshooting programs into their systems, containers, and infrastructures. Let's dive into these best practices ...