for different operating Systems • Different packages for bare metal, virtual machines, cloud instances, and containers Building and running applications is painful
information is actively sought – responsibilities are shared – cross-functional collaboration is encouraged and rewarded – failures are treated primarily as opportunities to improve the system – failures are learning opportunities, and messengers of them are not punished
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
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
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
on Risk Measuring the quality of software change HIGH IT PERFORMERS MEDIUM IT PERFORMERS LOW IT PERFORMERS On-Demand Week - Month Month - 12 Months < 1 Hour Week - Month Month - 6 Months USE CASES INCLUDE: ▪ Compliance Automation ▪ Compliance Coverage COMPLIANCE AUDIT FREQUENCY TIME DEPLOYING REMEDIATION