--- title: "DevOps Metric: Amount of Defects and Issues: definition." url: "https://pipelinedriven.org/article/devops-metric-amount-of-defects-and-issues-definition.md" canonical: "https://pipelinedriven.org/article/devops-metric-amount-of-defects-and-issues-definition" published: "2016-10-29T09:10:27.276000+00:00" updated: "2016-10-29T09:10:27.585000+00:00" tags: [] author: "Roy Osherove" description: "Important to : VP of QA, Operations Definition : How many bugs or tickets are found in production/ how many recurring bugs in production. As well as - how…" usage: "Licensed under CC BY 4.0 — reuse, quote and adapt with attribution (Roy Osherove, link to the original page)." license: "https://creativecommons.org/licenses/by/4.0/" --- # DevOps Metric: Amount of Defects and Issues: definition. 29 October 2016 · 1 min read · Roy Osherove - **Important to**: VP of QA, Operations - **Definition**: How many bugs or tickets are found in production/ how many recurring bugs in production. As well as - how many deployment issues during release are encountered. - **How to measure**: tickets from customers, support records. For deployment issues: post release retrospectives. - **Expected Outcome**: Amount of deployment issues, defects and recurring defects should decrease as DevOps maturity grows. Many organizations make an almost-conscious choice: go fast, or build with high quality. Usually they lose on both ends. Measuring defects and deployment issues is a good measure for a DevOps maturity model. You should become faster while not compromising on quality, because quality gates are fully automated in the form of tests in multiple steps, instead of manual error prone steps. The same applies for error prone deployments: they almost stop happening, and when they do happen, the deployment script itself is fixed and can be tested before being used to deploy to production. Just like regular software development life cycles. The ROI is huge. --- ## About the author **Roy Osherove**: Senior Solutions Architect at AWS working on AI for production and AI-driven development; author of The Art of Unit Testing and Elastic Leadership, with about 20 years of consulting and training on unit testing, TDD, team leadership and continuous delivery. ### Sites - [RobotPaper](https://robotpaper.ai/): This blog: AI patterns and anti-patterns, AI and coding agents, and engineering leadership. - [osherove.com](https://osherove.com): Roy's personal site. Author of The Art of Unit Testing and Elastic Leadership; consulting and training on unit testing, TDD, team leadership and continuous delivery, plus about 20 years of blog posts. - [The Art of Unit Testing](https://www.artofunittesting.com): The Art of Unit Testing, 3rd Edition (Manning): readable, maintainable, trustworthy unit tests, plus TDD workshops in C#, JavaScript, Java and Kotlin. - [5whys.com](https://www.5whys.com): Roy's writing on software team leadership: self-organizing teams, surviving chaos, learning mode and the Elastic Leadership model. - [Pipeline Driven](https://pipelinedriven.org): Continuous delivery and DevOps practices: build patterns, pipeline-friendly testing, DevOps metrics and enterprise DevOps. - [Elastic Leadership](https://www.elasticleadership.com): Elastic Leadership, Roy's framework for software team leaders (survival, learning and self-organizing modes). ### Social - X: https://x.com/royosherove - LinkedIn: https://www.linkedin.com/in/osherove/ ### Contact - Contact form: https://forms.gle/jQSx5KoXvrVA1JCK7 ### License Licensed under CC BY 4.0 — reuse, quote and adapt with attribution (Roy Osherove, link to the original page). License: https://creativecommons.org/licenses/by/4.0/