There are certain inalienable truths about businesses: they all want to succeed and they all want to beat their competitors. What's slightly different is how a business defines success. For a healthcare company, it might be lives saved. For an insurance company, it's the number of policies bought. For an e-commerce retailer, it's shopping basket conversions.
Quality assurance (QA) used to be a compliance activity. You were releasing a product and needed to test it and stamp it “approved.” QA was about testing that the code worked. You might manually test the code. You might have even tried some automation — coding a set of test scripts that would try to capture regressions or errors that you had eradicated in the past, but which somehow crept back in. All in all, you were reasonably satisfied that you achieved a level of test coverage that met your goals. Then, you put your code into production and crossed your fingers that nothing went wrong. And if it did, you tried to fix it as quickly as humanly possible.
For a while now (about 10 years), Dev and Ops have been trying to get along. After all, collaboration between the two creates fast feedback loops and gets high-quality software into users’ hands faster. But with a new space emerging, digital experience management, Dev and Ops need to make a new BFF—the business—to stay in sync.