Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

The Mainframe: Transitioning to a DevOps Culture

DZone's Guide to

The Mainframe: Transitioning to a DevOps Culture

Can the mainframe community successfully make the transition to a culture more in-line with the DevOps movement? Let's explore some of the challenges.

· DevOps Zone ·
Free Resource

DevOps involves integrating development, testing, deployment and release cycles into a collaborative process. Learn more about the 4 steps to an effective DevSecOps infrastructure.

I recently participated in a panel discussion at Share in Providence, Rhode Island. We were discussing and exploring the cultural challenges facing mainframe teams as they embrace DevOps practices.  Here are some of my observations:

Firstly DevOps is not an option for the mainframe, it is mandatory in my opinion. For too long the mainframe was the quiet “enterprise” citizen residing in the basement, making the world go around. As long as there was high availability and high CICS or IMS transaction rates, all was good. The mainframe has endured through many decades of technologies, boom and bust economies, and space shots. It has an amazing story and is arguably the most advanced platform in the world.

So Where Is the Challenge?

But, as the panel discussed – there are challenges facing the mainframe:

  • The Baby Boomer generation makes up the vast majority of the current mainframe demographic and with their retirements already upon us, how are companies going to attract new, younger talent to develop and maintain mainframe apps?

  • Many believe you have to be agile or implement a bimodal strategy to do DevOps on the mainframe; however, neither is true. Accelerating application delivery is the number one reason companies implement agile development methodologies, but agile by itself is often not sufficient, and bimodal does not work well either as it just creates bigger silos that do not map with the value stream of the business

  • The era of large, infrequent, monolithic software releases is over. Modern applications are supported across a complex, distributed and heterogeneous set of environments, and frequent changes to the systems of engagement tend to drive changes to the systems of record, requiring organizations to improve the flow of change through all systems in the value chain.

It’s no longer about MTBF (Mean Time Before Failure) but about MTTR (Mean Time to Repair). It’s no longer about strength but about resilience. Define the desired characteristics, actions, and behaviors, then design or update the system to reinforce those behaviors.

Culture is an organization’s pattern of responses to the problems and opportunities it encounters. It starts with culture and people and ends with business value. Only with a DevOps culture will the mainframe environment attract new talent and deliver at the speed the business requires while still maintaining the mainframe legacy of quality and security. Mainframers were the original unicorns, they need to rise up again to the challenge.

Want to learn more? Check out the latest DevOps Drive-in with DevOps author Gary Gruver on scaling DevOps in brownfield environments.

Read the 4-part DevOps testing eBook to learn how to detect problems earlier in your DevOps testing processes.

Topics:
devops ,mainframe ,ci/cd

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}