Some of this blog post was originally scheduled for late last year but didn’t publish. I’ve taken that content and added to it — I think you’ll find it all relevant.
The first note up is on a topic that has long been a topic of client inquiries: the relationship between DevOps and mainframes. This is a fairly frequent discussion topic, often a point of deliberation with our large enterprise clients. In Extend DevOps Across the Enterprise by Developing on the Mainframe, Thomas Klinect addresses: “The availability of DevOps toolchains on mainframes can help the platform keep pace with modern agile environments, but I&O leaders face obstacles to their use, from culture to process to integration. This research explains how to add the mainframe to your DevOps strategy.”
Another note of interest is around ensuring your teams are aligned correctly: Adapt Your Application Architecture Practices to Work Better With DevOps Teams — “By aligning your application architecture team’s working practices with those of your DevOps teams, you can ensure the success of your DevOps initiative and overcome resistance to architecture requirements.”
Directly pertinent research note related to this topic is “Balance Velocity and Risk by Having DevOps Teams Earn Leaner Processes” It covers “Adoption of DevOps creates a conflict between DevOps teams trying to increase the rate of value delivery and governance policies designed to manage risk. I&O leaders should define a set of leaner change control processes and build a path for teams to earn the right to use them.” This note comes in conjunction with a very handy toolkit “Toolkit: Assessing DevOps team continuous delivery risk“
Till next post – chris
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.