The trail to mainframe agility
When Compuware, now a BMC firm, got here beneath new management in 2014, the corporate launched into a mission to realign as an Agile enterprise. It went from delivering buyer necessities each 12 to 18 months to a publicly confronted quarterly roadmap deeply engaged with clients. As soon as the corporate began to see some success, clients went from asking “Why ought to I do Agile improvement and DevOps on the mainframe” to “How do I do Agile and DevOps on the mainframe?” in accordance with Sam Knutson, vp of product administration at Compuware.
RELATED CONTENT: Mainframe for DevOps places an finish to silos
To assist others reap the advantages, Compuware has offered 10 steps to reaching mainframe agility:
Decide your present and desired state: Be clear about what you are attempting to attain and what the transformation will seem like, then map out a plan.
Modernize your mainframe improvement setting: Transfer away from inexperienced display screen ISPF environments that require specialised abilities and information into extra trendy improvement areas. It will open up the expertise pool of builders out there to work on the mainframe.
Undertake automated testing: In a current report, the corporate discovered that take a look at automation is essential for accelerating innovation with 90% of IT leaders saying automating extra take a look at instances is the only most necessary issue of their success. Moreover, 92% of respondents mentioned mainframe groups spend extra time testing code due to the rising software setting complexity. Automated testing will unlock developer time and supply quick suggestions on the mainframe.
Present graphical intuitive visibility into current code and information construction: Builders want a fast and straightforward solution to perceive the applying logic, interdependencies, information buildings, information relationships and runtime behaviors to make sense of what’s happening.
Empower builders in any respect talent and expertise ranges: There will not be a variety of new mainframe builders popping out of faculty, so the following era of builders should be coached and educated if firms need to enhance improvement efficiency and productiveness on the mainframe.
Provoke coaching in and adoption of Agile processes: As soon as trendy improvement environments are arrange, groups can begin coaching and shift from a waterfall to an Agile method. Mainframe builders ought to be paired with Agile builders to allow them to study from one another.
Leverage operational information throughout the event, testing and manufacturing life cycle: Builders have to grasp how the applying is behaving so as to enhance it and so they can do this by trying on the operational information repeatedly and measuring progress.
Deploy true Agile/DevOps-enabling supply code administration: Conventional supply code administration environments had been designed for waterfall. A contemporary, Agile SCM setting ought to present automation, visibility, rules-based workflows, and integration with different instruments.
Automate deployment of code into manufacturing: Getting new code out rapidly and reliably into manufacturing requires autoating and coordinating deployments in a synchronized method and with the ability to pinpoint any points as they happen.
Allow coordinated cross-platform steady supply: Mainframes shouldn’t be disregarded of the pipeline. It ought to turn out to be simply one other platform that may be up to date rapidly and adapt as needed.
“To stay aggressive in an app-centric economic system, mainframes should be as adaptive as different platforms. And enterprise IT should have the ability to handle DevOps in an built-in method throughout mainframe, distributed and cloud,” the corporate wrote in a white paper.