<p>This is pretty deep in to "opinion based" but here goes:</p>

<p>While most definitions of "DevOps" are independent of specific tools and techniques, it is very often combined with things like test automation (e.g. Jenkins, Travis-CI) and deployment automation (e.g. Chef, Capistrano, Kubernetes). Those two together act as a forcing function to push up quality levels of software by making it both easier to use tests to ensure things don't break and making it easier to fix breakages when they do occur.</p>

<p>That said, I really doubt that number captures the full story. Like so many things, "software quality" is easy to talk about but difficult to define.</p>

CC BY-SA 3.0
2017-02-28T20:18:08.307Z
2017-02-28T20:18:08.307Z
coderanger
<p><a href="https://puppet.com/resources/whitepaper/2016-state-of-devops-report" rel="nofollow noreferrer">The DevOps Report by Puppet Labs</a> states that "devopsy" companies have 3x times lower failure rate. While other companies must have a fairly regular rate of failures from deployments to production.</p>

<p>What are the companies who have very low failure rates do differently?
How can other companies mimic such decrease in failures of changes in their production (and other) environments?</p>

CC BY-SA 3.0
2017-02-28T18:25:47.577Z
http://www.ciosummits.com/Online_Assets_Puppet_2016_State_of_DevOps_Report.pdf
Evgeny Zislis
<deployment><automation><culture><dtap>
How to prevent failure from introduced changes?
Evgeny Zislis
# How to prevent failure from introduced changes?

(Asked by: username_0 on 2017-02-28)

[The DevOps Report by Puppet Labs](https://puppet.com/resources/whitepaper/2016-state-of-devops-report) states that "devopsy" companies have 3x times lower failure rate. While other companies must have a fairly regular rate of failures from deployments to production.

What are the companies who have very low failure rates do differently?
How can other companies mimic such decrease in failures of changes in their production (and other) environments?

**Tags:** deployment, automation, culture, dtap

> **Comments:**
> **username_0**: http://www.ciosummits.com/Online_Assets_Puppet_2016_State_of_DevOps_Report.pdf  

---

## 1 answers

### Answer by username_1 on 2017-02-28. Score: 0

This is pretty deep in to "opinion based" but here goes:

While most definitions of "DevOps" are independent of specific tools and techniques, it is very often combined with things like test automation (e.g. Jenkins, Travis-CI) and deployment automation (e.g. Chef, Capistrano, Kubernetes). Those two together act as a forcing function to push up quality levels of software by making it both easier to use tests to ensure things don't break and making it easier to fix breakages when they do occur.

That said, I really doubt that number captures the full story. Like so many things, "software quality" is easy to talk about but difficult to define.


---

