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.
Achieve more with less. How many of you feel that pressure — or, even worse, hear those words — trickle down from leadership? The reality is that overworked and under-resourced IT departments will only lead to chronic errors, missed deadlines and service assurance failures. After all, we're only human. So what are overburdened IT departments to do? Reduce the human factor. In a word: automate ...
On average, data innovators release twice as many products and increase employee productivity at double the rate of organizations with less mature data strategies, according to the State of Data Innovation report from Splunk ...
While 90% of respondents believe observability is important and strategic to their business — and 94% believe it to be strategic to their role — just 26% noted mature observability practices within their business, according to the 2021 Observability Forecast ...
Let's explore a few of the most prominent app success indicators and how app engineers can shift their development strategy to better meet the needs of today's app users ...
Business enterprises aiming at digital transformation or IT companies developing new software applications face challenges in developing eye-catching, robust, fast-loading, mobile-friendly, content-rich, and user-friendly software. However, with increased pressure to reduce costs and save time, business enterprises often give a short shrift to performance testing services ...
DevOps, SRE and other operations teams use observability solutions with AIOps to ingest and normalize data to get visibility into tech stacks from a centralized system, reduce noise and understand the data's context for quicker mean time to recovery (MTTR). With AI using these processes to produce actionable insights, teams are free to spend more time innovating and providing superior service assurance. Let's explore AI's role in ingestion and normalization, and then dive into correlation and deduplication too ...
As we look into the future direction of observability, we are paying attention to the rise of artificial intelligence, machine learning, security, and more. I asked top industry experts — DevOps Institute Ambassadors — to offer their predictions for the future of observability. The following are 10 predictions ...
One thing is certain: The hybrid workplace, a term we helped define in early 2020, with its human-centric work design, is the future. However, this new hybrid work flexibility does not come without its costs. According to Microsoft ... weekly meeting times for MS Teams users increased 148%, between February 2020 and February 2021 they saw a 40 billion increase in the number of emails, weekly per person team chats is up 45% (and climbing), and people working on Office Docs increased by 66%. This speaks to the need to further optimize remote interactions to avoid burnout ...
Here's how it happens: You're deploying a new technology, thinking everything's going smoothly, when the alerts start coming in. Your rollout has hit a snag. Whole groups of users are complaining about poor performance on their devices. Some can't access applications at all. You've now blown your service-level agreement (SLA). You might have just introduced a new security vulnerability. In the worst case, your big expensive product launch has missed the mark altogether. "How did this happen?" you're asking yourself. "Didn't we test everything before we deployed?" ...
The Fastly outage in June 2021 showed how one inconspicuous coding error can cause worldwide chaos. A single Fastly customer making a legitimate configuration change, triggered a hidden bug that sent half of the internet offline, including web giants like Amazon and Reddit. Ultimately, this incident illustrates why organizations must test their software in production ...