Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Quantifying Outcomes - Efficient Service Stability

Quantifying Outcomes - Efficient Service Stability

Part 4 in a 4 part short-form interactive series

George Miranda

April 05, 2017
Tweet

More Decks by George Miranda

Other Decks in Technology

Transcript

  1. The impact of outperformance 5x Revenue Growth, 8x Profitability Growth,

    2x Shareholder Return Growth 4.3% 13.5 % 18.1 % 0.8% -1.8% 10.3% B2B digital leaders turn in stronger financial performance. Top-quartile digital B2B companies Rest of B2B sample Revenue growth, CAGR,2010-15 Operating profit (EBIT) Growth, CAGR, 2010-15 Return to shareholder (TRS) growth, CAGR, 2010-15 ~5X ~8X ~2X Firms with high performing IT organizations were twice as likely to exceed their profitability, market share, and productivity goals The State of DevOps, 2016 HIGH PERFORMING IT ORGANIZATIONS: ▪ 200x more frequent releases ▪ 24x faster at recovering from failures ▪ 3x lower change failure rate ▪ 255x shorter lead times No high velocity company has gotten there without automation as a foundation 2x
  2. Velocity: time from idea to ship Software success metrics Quantifying

    outcomes to deliver software at speed Deployment frequency Time from commit to deploy Mean time to resolve Time deploying remediation Change failure rate SPEED Measure of rate of software change EFFICIENCY Measure of effectiveness of software change RISK Measure of quality of software change Compliance audit frequency Idea Ship
  3. Speed Efficiency Risk Transformation Speed 50% Source: Audience poll 'Digital

    transformation & the competitive edge' Important transformation concerns Speed Efficiency Risk Transformation Risk 8.3%
  4. "How do you measure 'time from commit to deploy?' Is

    that average time, max time, or other? For example, in our environment we currently deploy once a quarter. Some commits are made months before deployment and some are made days or hours before deployment. How do we measure that?" Source: https://blog.chef.io/2017/04/03/quantifying-devops-outcomes-increasing-speed Q&A from "Increasing Speed" webinar
  5. Standard Bank pushes ideas from commit to deploy in 18

    minutes with Chef Focus on Speed Measuring the rate of software change HIGH IT PERFORMERS MEDIUM IT PERFORMERS LOW IT PERFORMERS On-demand Week - Month Month – 6 Month < 1 Hour Week - Month Month - 6 month USE CASES INCLUDE: ▪ Application Delivery ▪ Build Pipelines DEPLOYMENT FREQUENCY TIME FROM COMMIT TO DEPLOY
  6. Velocity: time from idea to ship Software success metrics Quantifying

    outcomes to deliver software at speed Deployment frequency Time from commit to deploy Mean time to resolve Time deploying remediation Change failure rate SPEED Measure of rate of software change EFFICIENCY Measure of effectiveness of software change RISK Measure of quality of software change Compliance audit frequency Idea Ship
  7. Velocity: time from idea to ship Software success metrics Quantifying

    outcomes to deliver software at speed Deployment frequency Time from commit to deploy Mean time to resolve Time deploying remediation Change failure rate SPEED Measure of rate of software change EFFICIENCY Measure of effectiveness of software change RISK Measure of quality of software change Compliance audit frequency Idea Ship
  8. Intuit reduced change failure rate by 90% with Chef Focus

    on Efficiency Measuring the effectiveness of software change HIGH IT PERFORMERS MEDIUM IT PERFORMERS LOW IT PERFORMERS 0-15% 31-45% * 16-30% < 1 Hour < 1 Day < 1 Day * USE CASES INCLUDE: ▪ Configuration Management ▪ Server Drift CHANGE FAILURE RATE MEAN TIME TO RESOLVE
  9. Pipeline shape VERIFY APPROVE COMMIT CHANGE BUILD ACCEPTANCE DELIVER UNION

    REHEARSAL DELIVERED Does the latch open & close?
  10. Pipeline shape VERIFY APPROVE COMMIT CHANGE BUILD ACCEPTANCE DELIVER UNION

    REHEARSAL DELIVERED Does the latch open & close? Is it smooth? Can I lock it?
  11. Pipeline shape VERIFY APPROVE COMMIT CHANGE BUILD ACCEPTANCE DELIVER UNION

    REHEARSAL DELIVERED Does the latch open & close? Is it smooth? Can I lock it? Put it on a door. Does it work on that door?
  12. Pipeline shape VERIFY APPROVE COMMIT CHANGE BUILD ACCEPTANCE DELIVER UNION

    REHEARSAL DELIVERED Does the latch open & close? Is it smooth? Can I lock it? Put it on a door. Does it work on that door? Try it on front door, back door, bathroom door, etc
  13. Pipeline shape VERIFY APPROVE COMMIT CHANGE BUILD ACCEPTANCE DELIVER UNION

    REHEARSAL DELIVERED Does the latch open & close? Is it smooth? Can I lock it? Put it on a door. Does it work on that door? Try it on front door, back door, bathroom door, etc Put that latch on all doors in a house. Run all the tests.
  14. Pipeline shape VERIFY APPROVE COMMIT CHANGE BUILD ACCEPTANCE DELIVER UNION

    REHEARSAL DELIVERED Does the latch open & close? Is it smooth? Can I lock it? Put it on a door. Does it work on that door? Try it on front door, back door, bathroom door, etc Put that latch on all doors in a house. Run all the tests. Install that latch on all doors in prod
  15. Intuit reduced change failure rate by 90% with Chef Focus

    on Efficiency Measuring the effectiveness of software change HIGH IT PERFORMERS MEDIUM IT PERFORMERS LOW IT PERFORMERS 0-15% 31-45% * 16-30% < 1 Hour < 1 Day < 1 Day * USE CASES INCLUDE: ▪ Configuration Management ▪ Server Drift CHANGE FAILURE RATE MEAN TIME TO RESOLVE
  16. Intuit reduced change failure rate by 90% with Chef Focus

    on Efficiency Measuring the effectiveness of software change HIGH IT PERFORMERS MEDIUM IT PERFORMERS LOW IT PERFORMERS 0-15% 31-45% * 16-30% < 1 Hour < 1 Day < 1 Day * USE CASES INCLUDE: ▪ Configuration Management ▪ Server Drift CHANGE FAILURE RATE MEAN TIME TO RESOLVE
  17. LOB LOB FOCUS ON SPEED Tension caused by the demands

    placed on teams… …can be resolved by vertical integration and automation… …to deliver a future of developer services and software at speed SHARED SERVICES Vertical Integration is key to velocity A balance of increasing speed, improved efficiency and decreasing risk FOCUS ON RISK SHARED SERVICES LOB Line of Business LOB Line of Business LOB SHARED SERVICES LOB DEVELOPER SERVICES BUILD • DEPLOY • MANAGE • COLLABORATE
  18. ” Business Value with Developer Services Shifting capabilities to match

    business requirements Developer Services Engineer Line of Business Development Team I provide services that developers and development teams use to build and deliver applications. Developer Services Teams Traditional Central IT System Administrator Centralized Enterprise IT Team I manage and deliver infrastructure required to run software in my organization. Enabling development teams to get insights into speed, efficiency and risk of delivery of their software Reducing risk to my organization from my infrastructure and software that runs on it Enabling development teams to ship software at speed while maintaining quality and reducing risk Reliably managing changes to infrastructure requirements Providing on-demand, self-service infrastructure and services tailored to developer needs Managing and lowering costs of running, configuring, and maintaining infrastructure DEPLOY MANAGE Don’t measure me on traditional IT metrics, but on the metrics of the business Jim Fowler, CIO, GE Capital BUILD Reducing friction by enabling full stack transparency and management capability with separation of duties Delivering configured infrastructure and handing off responsibility to development teams COLLABORATE
  19. The Chef Automate Platform Continuous Automation for High Velocity IT

    Workflow • Local development • Integration • Tooling (APIs & SDKs) COLLABORATE ▪ Package ▪ Test ▪ Approve BUILD ▪ Provision ▪ Configure ▪ Execute ▪ Update DEPLOY ▪ Secure ▪ Comply ▪ Audit ▪ Measure ▪ Log MANAGE Infrastructure Automation Compliance Automation Application Automation OSS AUTOMATION ENGINES Increase Speed ▪ Package infrastructure and app configuration as code ▪ Continuously automate infrastructure and app updates Improve Efficiency ▪ Define and execute standard workflows and automation ▪ Audit and measure effectiveness of automation Decrease Risk ▪ Define compliance rules as code ▪ Deliver continuous compliance as part of standard workflow
  20. Q&A George Miranda Technical Strategy Chef Software, Inc. @gmiranda23 .

    What challenges do you face when implementing your transformation initiatives?