effectiveness of DevOps practices. Why Measure DevOps? • To measure software delivery throughout and stability to understand how teams can improve. • Make data-based decisions rather than relying on gut instinct. • To identify pain points and slowness in pipelines and processes.
you compare? Deployment Frequency - Elite: On-demand (multiple deploys per day) - High: Once/day - Once/week - Medium: Once/week - Once/Month - Low: Once/month - Once/6 months Lead Time For Changes - Elite: Less than 1 day - High: 1 day - 1 week - Medium: 1 week - 1 month - Low: 1 month - 6 months Change Failure Rate - Elite, High and Medium : 0-15% - Low: 46-60% - Time To Restore Service - Elite: Less than 1 hour - High and Medium: : Less than 1 day - Low: 1 week - 1 month Source : State of DevOps 2019
of product, version, or sprint. • Maps time spent on issues over specified time - Lead Time for change: Can be derived by using the Control Chart https://www.atlassian.com/software JIRA - Control Chart
process - Continuous Integration / Continuous Delivery(deployment) - Version Control How to Improve Software Delivery Performance • Leverage Cloud Services • Change Approval Process • Implement Test Automation • Proactive Monitoring