2

The DevOps Report by Puppet Labs 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?

closed as too broad by Gepser, kenorb, 7ochem, soundslikeodd, Peter G Feb 28 '17 at 22:15

Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.

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.

Not the answer you're looking for? Browse other questions tagged or ask your own question.