Taking a Low-Risk Approach to DevOps for Mainframe Organizations - Part 1
July 16, 2018

Mark Levy
Micro Focus

After more than 40 years of investment, Enterprise IT runs the business world on applications that span many different development methodologies and infrastructure architectures — from mainframe to mobile. In today's digital age, delivering new application innovation faster is imperative to driving business success. As such, to remain competitive, large enterprise IT organizations must scale DevOps practices across their traditional and hybrid IT environments.

For many of the world's largest enterprises, the mainframe is the core business engine. Over 90 percent of the top 100 banks and all of the top 10 insurance companies use mainframes. COBOL applications connect 500 million mobile users on a daily basis and power 70 percent of all business transactions. There are far more COBOL transactions per day than Google and YouTube searches combined.

Yet mainframe teams still struggle with scaling DevOps practices. To start, improving mainframe collaboration and technical flexibility is challenging, as teams are often siloed and used to working with long established, non-Agile development practices. This can lead to a lack of cross-team engagement and collaboration. Additionally, change on the mainframe requires specialized development tools and iterative, linear processes that creates bottlenecks. Finally, testing capacity for the mainframe is inflexible and cost prohibitive – creating yet another roadblock when it comes to successfully growing out DevOps practices.

The key to mainframe DevOps success is in quickly identifying and removing major bottlenecks in the application delivery lifecycle. Major challenges include collaboration between mainframe and distributed teams, lack of visibility into the impact of software changes, and limited resource flexibility with scaling out necessary testing initiatives. Now let's take a closer look at some of these key challenges and how IT departments can address them.

Lack of Collaboration Between Mainframe and Distributed Teams

The mainframe has historically existed in its own silo, running separately from the rest of IT. To those on the outside, it has always been viewed as a ‘black box' rather than a cross-functional component of the department. Most mainframe organizations are centralized with specialized highly-skilled experts who are organized into separate groups. Over the years, they have developed mature processes with a set of mainframe-specific tools to manage software changes slowly and deliberately. This has produced an incredibly stable and reliable platform.

So what's the problem? To scale DevOps practices and deliver at the speed the business requires, siloes must be removed from the mainframe. However, the idea of breaking up the mainframe silo is a bit unsettling to the mainframe community. Culturally, the mainframe community looks at the world in a way that puts itself in conflict with the more dynamic nature of DevOps. There needs to be a cultural shift driving this change toward inclusiveness, especially as older IT workers retire. Millennials will be replacing the baby boomer mainframe software developers and will demand modern mainframe tools and practices. To help, senior management will need to break down the barriers between mainframe and distributed application teams and treat the mainframe like any other enterprise IT platform.

Lack of Visibility into the Impact of Software Change

Today's modern n-tier architecture is supported by many different teams, processes, and toolchains across many different platforms and application infrastructures. Lack of visibility into the impact that software change will have on applications makes it difficult to gain an integrated, real-time view across the deployment pipelines. This creates many blind spots where organizations must rely on doing manual work – pushing defects downstream and driving rework numbers up.

Limited Resource Flexibility to Scale Necessary Testing

Traditionally mainframe delivery processes are based on a sequential, waterfall method for planning and resource allocation. Precious mainframe resources – specifically machine and human – are also time-bound, which creates a rigid framework where flexibility and scale is difficult. Missed delivery milestones can lead to long delays until mainframe resources are available again. This rigid framework is incompatible with DevOps practices and a major constraint for mainframe development teams.

While mainframe challenges are vast and varied, they definitely aren't unsurmountable. In part 2 of this series on taking a low risk approach to mainframe DevOps, I'll delve into specifics around how teams can capture value along each step of the journey.

Read Taking a Low-Risk Approach to DevOps for Mainframe Organizations - Part 2

Mark Levy is Director of Strategy at Micro Focus

The Latest

August 15, 2018

Microservices are a hot topic in IT circles these days. The idea of a modular approach to system building – where you have numerous, smaller software services that talk to each other instead of monolithic components – has many benefits ...

August 13, 2018

Agile is expanding within the enterprise. Agile adoption is growing within organizations, both more broadly and deeply, according to the 12th annual State of Agile report from CollabNet VersionOne. A higher percentage of respondents this year report that "all or almost all" of their teams are agile, and that agile principles and practices are being adopted at higher levels in the organization ...

August 09, 2018

For the past 13 years, the Ponemon Institute has examined the cost associated with data breaches of less than 100,000 records, finding that the costs have steadily risen over the course of the study. The average cost of a data breach was $3.86 million in the 2018 study, compared to $3.50 million in 2014 – representing nearly 10 percent net increase over the past 5 years of the study ...

August 08, 2018

Hidden costs in data breaches – such as lost business, negative impact on reputation and employee time spent on recovery – are difficult and expensive to manage, according to the 2018 Cost of a Data Breach Study, sponsored by IBM Security and conducted by Ponemon Institute. The study found that the average cost of a data breach globally is $3.86 million ...

August 06, 2018

The previous chapter in this WhiteHat Security series discussed dependencies as the second step of the Twelve-Factor App. This next chapter examines the security component of step three of the Twelve-Factor methodology — storing configurations within the environment.

August 02, 2018

Results from new Forrester Consulting research reveal the 20 most important Agile and DevOps quality metrics that separate DevOps/Agile experts from their less advanced peers ...

July 31, 2018

Even organizations that understand the importance of cybersecurity in theory often stumble when it comes to marrying security initiatives with their development and operations processes. Most businesses agree that everyone should be responsible for security, but this principle is not being upheld on a day-to-day basis in many organizations. That’s bad news for everyone. Here are some best practices for implementing SecOps ...

July 30, 2018

While the technologies, processes, and cultural shifts of DevOps have improved the ability of software teams to deliver reliable work rapidly and effectively, security has not been a focal point in the transformation of cloud IT infrastructure. SecOps is a methodology that seeks to address this by operationalizing and hardening security throughout the software lifecycle ...

July 26, 2018

Organizations are shifting away from traditional, monolithic architectures, with three-quarters of survey respondents delivering at least some of their applications and more than one-third delivering most of their applications as microservices, according to the State of DevOps Observability Report from Scalyr ...

July 24, 2018

What top considerations must companies make to ensure – or at least help improve – Agile at scale? The following are key techniques and practices to help accelerate Agile delivery rollouts and scale Agile and DevOps in the Enterprise ...

Share this