This is the third in a series of three blogs directed at recent EMA research presented in a webinar on April 11, with replay now available. The first blog provided a general introduction to the highlights of the research, while the second blog focused more on organization and process.
In this blog we'll look at three areas that have emerged in a spotlight in and of themselves — as signs of changing times — let alone as they may impact digital war room decision making. They are the growing focus on development and agile/DevOps; the impacts of cloud; and the growing need for security and operations (SecOps) to team more effectively.
But first a few key takeaways from the first two blogs to ground new readers and remind past readers:
■ These insights and data points are taken from research done in Q1 of this year across 272 respondents in North America and Europe.
■ We left open — to our respondents — whether the digital war room was virtual, physical, or hybrid. (The majority were hybrid. Purely virtual were the least strongly represented.)
■ We found that the digital war room was, on the whole, a: growing, b. becoming more important as well as more inclusive; c. was generally moving toward a more defined and less ad hoc role; d. was becoming, at least by implication, more proactive.
The growing inclusiveness of the digital war room is, needless to say, foundational to our examination of the role of development and DevOps, cloud and SecOps discussed below.
Development and Agile/DevOps — a Growing Role for War Room Integration
Industry dialogs sometimes point to an agile revolution that's effectively dismantling the role of the war room, IT service management teams, and even central operations as a whole. And while the value of unique DevOps teams to coalesce around targeted applications shouldn't be dismissed, the parallel need for a central authority to handle full-stack concerns with an eye to business as well as IT priorities too often gets overlooked.
The digital war room research shines a light on what's really going on here. When we asked Over the last two years, how have development teams worked with operations and other teams in digital war room decision-making? We received the following answers:
■ Development has become more involved in war room decision making (37%)
■ Development's role has remained the same in war room decision making (32%)
■ Agile/DevOps has led to a separate track for war room decision making (16%)
■ Development has become less involved in war room decision making (15%)
In other words, 69% saw development as having either a growing role, or having a sustained role in the digital war room.
Moreover, when we tracked success rates in assuring overall service delivery and service performance, we saw dramatic alignment with those respondents where development had become more involved. Then, when we asked what respondents hoped for in the future, we saw that:
■ 39% indicated that development should become more involved in the digital war room.
■ 25% felt the level of development's involvement should stay the same.
■ 19% felt that development should become less involved.
■ 17% felt there should be a separate track for agile/DevOps decision making.
In other words — the trend toward war room inclusion of development and DevOps teams should continue along somewhat even lines. And once again, success rates favored those targeting increasing development/war room inclusion.
So then, how exactly does development team with operations in the digital war room? The answers, in ranked order, were, via:
■ A shared IT alerting system
■ Shared insights into end-user experience
■ Shared monitoring
■ Shared analytics
■ Incident alerts from the service desk
■ Social media for team-mode collaboration
■ Shared KPIs and alerts
Areas such as shared insights into end-user experience, shared analytics, and social media all point to proactive collaboration critical for DevOps and agile concerns as well as core incident handling — indicating a significant value for lifecycle application optimization.
The "Journey to the Cloud" — Good or Bad for Digital War Room Performance?
In our research, the average response indicated that about 20% of their workloads were in the public cloud, while 15% indicated that 50% or more were in the public cloud. So, was this good or bad for digital war room effectiveness? The answer was overall encouraging:
■ 50% claimed that cloud has made digital war room decision-making easier
■ 41% felt it was making things in the war room harder
■ Only 9% saw no change
When we asked those who felt cloud was making war room decision-making more difficult about the major reason why — the answers, in ranked order, were:
■ Cloud is requiring new skill sets and internal processes
■ Cloud has challenged war room efficiencies due to migration issues
■ Cloud is requiring new processes for interacting with cloud service providers
Security and Insecurity in the Digital War Room
In almost all my research, there are growing indications that security is becoming an ever more present concern for operations and ITSM teams more broadly. And in some unique SecOps research that EMA did last year, the movement is clearly bi-directional, or in other words a shared need that benefits both groups.
In terms of the digital war room, here are a few relevant highlights:
■ 32% of our respondents had some security-related involvement.
■ After ITSM and executive IT, the third most likely to own the digital war room was security/compliance/GRC/incident response.
■ Improved network security was tied with service performance when it came to optimizing war room performance in hybrid cloud environments. These were followed by integrated security and performance and integrated security and change.
■ Advanced IT Analytics (AIA), security information and event management (SIEM), and security threat intelligence and analysis led as the top three technologies for war room decision making.
■ Security-related issues led as the biggest roadblock to effective war room success.
Beyond all these data points, what should stand out is the growing role of digital war rooms in unifying IT in support of critical, cross-domain (including development) decision making. This may be a surprise to some. It was partly a surprise to me. But I was happy to see these war-room affirming results.
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 ...