Code is only creating value for the business when it is being used by customers. So we’ve focused more on the natural flow and use the working definition of “lead time” as being shorthand for “code commit to production use by a customer lead time”. That’s the I&O focus for their portion of product delivery and addresses the classic question “how quickly can you meet business requirements to put code into production?” This research goes into a lot more yet is a very short read. I recommend a look.
Another note out this month is a drill down on details based on the first recommendation from the June note “Three Essential DevOps Actions to Perform When Dev Groups Go Agile). Agile Methodology has an immediate and blunt impact on I&O and we identify what those will be so I&O leaders can plan accordingly. So if June’s high-level note isn’t detailed enough and you want deeper insight into its’ first recommendation (basically guidance on how to “operationalize Dev”) this note will help:
We continue to see interest in Google’s SRE approach and are introducing publications on that. Site Reliability Engineering has many interesting features for I&O leaders to consider. Our first note is out this month and entitled:
And last, an Impact Appraisal announcing a change in how we do coverage. Given the market evolution, we are renaming the MQ and CC for Application Release Automation to Application Release Orchestration. This note explains why:
To be notified of new DevOps research as it’s published, click here!
View Free, Relevant Gartner Research
Gartner's research helps you cut through the complexity and deliver the knowledge you need to make the right decisions quickly, and with confidence.Read Free Gartner Research
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.