Steve Jones - SSC Editor wrote:
DevOps isn't related to cadance or QA/testing. It is related to learning to become better. Plenty of companies conflated the two and drove speed over quality (many still do). This isn't a tradeoff. Releasing every two weeks or every month isn't related to development time and testing.
DevOps preaches learning to become better, adapting your process, and improving quality. That's the goal. A feature still might take a month to develop and 2 weeks to test. That's fine. The idea is that once it is tested, it gets released ASAP, not delayed for another month. If you want to release every month, then that means you need multiple teams or multiple pieces of work moving concurrently because everything takes two weeks to test.
Microsoft, like many companies, makes mistakes. They continue to aim for improvement, and they've learned to adapt and improve their testing. Where they are is miles beyond releasing Visual Studio, or any other tool, every 3-4 years. That's DevOps.
DevOps isn't getting rid of QA, it's getting that function more tightly integrated into the software development process
Well, customers disagreed. 🙂 They do not LIKE rapid cadence, even when there aren't bugs. DevOps, in some respects, is about speed. The only advantage most users see in rapid cadence is fixing bugs. Which are better handled by QA so they don't exist in the first place.
Is 3-4 years, large changes, and Waterfall better? No, not necessarily. But DevOps conflates small releases (good for quality) and rapid cadence (get the features to the customers ASAP). It's the classic pendulum. As with everything the best place to be is in the middle rather than the extremes.
DevOps is much better suited to in-house development, in my opinion. It's also good for lone-wolf development where you can't get QA departments. Big companies with monstrous applications (Visual Studio, Windows, SQL Server, Oracle) should slow their cadence, depend less on DevOps alone, and invest in QA more heavily.