DevOps Without Measurement is a Fail

Editor's Notes

• #3: “DevOps has crossed the chasm.” 2019 Accelerate State of DevOps report, produced by DevOps Research & Assessment (DORA), Just a few years ago, many organizations still viewed DevOps more as a promising experiment than as a mainstream approach to software development. Today, however, as this year’s report shows, DevOps has secured its position as a proven and powerful set of practices and tools—giving teams the ability to make dramatic improvements in their performance and productivity.
• #4: As important as these advantages are, here’s an even more impressive metric: elite performers are twice as likely as low-performing teams to meet or exceed their organizational performance goals. DevOps transformation requires investments in an organization’s code pipeline, testing, instrumentation and monitoring, and other capabilities.
• #5: Siloed teams often lacks aligned measures for success 
• #6: New Relic has our own DevOps journey. New Relic went from a Ruby monolith, to a Ruby front-end and a Java backend, to microservices. We released infrequently, and our operations teams were separate from developers. Because of our success, we had to scale, and we took drastic action and change our teams and how we built software. Our products are now made up of more than 300 microservices (we were an early adopter of Docker). We have over 50 engineering teams with embedded SREs. Each team pushes their own code to production and is responsible for running what they’ve created. Hopefully, our experience can help you.
• #9: We have a three-phase measurement framework for a successful DevOps journey: Prepare - you need to be able to see everything with instrumentation across all of your technologies and measure your current state Activate - Monitor and quickly surface the information that will allow to fix problems fast Optimize - Continue to automate, and replicate DevOps practices across the organization.
• #12: Latency The time it takes to service a request. Traffic A measure of how much demand is being placed on your system - transactions per second Errors - The rate of requests that fail, either explicitly (e.g., HTTP 500s), implicitly Saturation How "full" your service is. A measure of your system fraction, emphasizing the resources that are most constrained. Quickstart: Apdex 4 golden signals 1-3 key transactions (from your Product Manager)
• #19: In addition to reliability and scalability, SREs are responsible to make sure the infrastructure can scale -- WITHOUT a 1:1 scaling in cost!
• #20: In a world where 50% of companies admit customers more likely to uncover problems before the company does(1), don’t lose sight of CUSTOMER EXPERIENCE. New Relic, in partnership with Vanson Bourne, led a survey of 750 global senior IT leaders at enterprises with 500 to 5,000 employees in the United Kingdom, Australia, France, Germany, and the United States. Customers don’t see or care about all the complexity going on behind the scenes. They don’t care about some third-party service that might have dragged your mobile app down or the complexity of your fulfillment workflow. When you peel back the motivations behind cloud migrations, DevOps, containerization, microservices, continuous integration/continuous deployment, single-page applications, and more, these trends are all enablers to make it easier, faster, or cheaper to push out better digital experiences to customers. Remember, it’s never been about the technology—it’s always been about the value and experience you’re delivering to the human being on the other side of that digital screen...and measurement can help
• #21: These are the Solution Patterns in our DevOps Solution Guide, in which we provide in-depth direction how to move forward with Devops. They are sequential; though it is NOT mandatory that you do all the patterns. We suggest you pick a place to start and move forward from there. Tutorials for these patterns are on the New Relic Docs site > Search for “DevOps”