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

January 17, 2019

To better align business and IT objectives, enterprise organizations should focus on the core "problems" that individual business units face today in driving out real consumer value. Until the roadblocks and inhibitors — and, ultimately, the resultant technical debt — are removed from the equation, large enterprise organizations will continue struggling to succeed ...

January 16, 2019

Technical debt is what results when legacy platforms or highly integrated and dependent systems and processes inhibit large enterprise organizations from meeting the needs of internal business stakeholders. In many cases, the core objectives that drive real, monetizable business value are not aligned to the esoteric IT goals of "automation" and "Agile development." This creates a fundamental disconnect between business and IT ...

January 14, 2019

Budget season is an important time of the year for businesses because it gives senior IT and security leaders time to reflect on what went right this year and what initiatives need to be given priority in the new year. Recent research from Threat Stack shows security budgets are expected to increase by 19 percent over the next two years, but business leaders are still facing challenges determining where to allocate this budget in the face of rapidly evolving infrastructure ...

January 10, 2019

As organizations of all sizes are embracing hybrid and multi-cloud infrastructures, they are experiencing the many benefits of a more agile, distributed and high-speed environment where new applications and services can be built and delivered in days and weeks, rather than months and years. But as the adoption of these next generation architectures continues to grow, so do the complexities of securing the cloud workloads running on them ...

January 09, 2019

DEVOPSdigest invited DevOps experts for their predictions on how DevOps and related technologies will evolve and impact business in 2019. Part 9, the final installment, covers microservices, containers and APIs ...

January 08, 2019

DEVOPSdigest invited DevOps experts for their predictions on how DevOps and related technologies will evolve and impact business in 2019. Part 8, covers microservices and containers ...

January 07, 2019

DEVOPSdigest invited DevOps experts for their predictions on how DevOps and related technologies will evolve and impact business in 2019. Part 7, covers the Cloud ...

December 20, 2018

DEVOPSdigest invited DevOps experts for their predictions on how DevOps and related technologies will evolve and impact business in 2019. Part 6, covers DevOps Analytics, including AI and Machine Learning ...

December 19, 2018

DEVOPSdigest invited DevOps experts for their predictions on how DevOps and related technologies will evolve and impact business in 2019. Part 5 is all about testing ...

December 18, 2018

DEVOPSdigest invited DevOps experts for their predictions on how DevOps and related technologies will evolve and impact business in 2019. Part 4 covers Agile, CI/CD and automation ...

Share this