DevOps is, by one description, Agile for Ops or IT. With closer input and collaboration from the business side, development and operations are using great tools to help Ops be more Agile and migrate code to production faster. But this can be complicated.
Companies that say they do DevOps or are accepting Devops but have very few in place to do so, or worse, have no idea what they are doing. This retells me of a few organizations that I knew in the Agile edge, that said they were Agile but were not. We all are at the time in DevOps where the usage of a single tool or single modification had uninformed people create consideration about an entire paradigm shift. And I’m sad to see this trend continuing.
If, a decade years before, you released phased quarterly releases to fix two weeks sprints with user stories in the place of requirements and your development team started using Jenkins for CI. That, by itself, did not make you Agile. It took many companies years to execute, figure out and tune the new methods. Like “ScrumButt,” we even already have a few anti-names — DevFlops and DevOops. But let’s not go there. Let’s do it right! There is great progress to be made here. DevOps, like Agile, is about culture.
In DevOps, the entire company concentrates on the business restraints and requirements rather than the whole company working according to development or Operations plan. Product features and cycles are completed when the business required it rather than being at the mercy of development and/or IT/Ops.
DevOps is also more about business modification and Operations/IT modification than Development and Testing change. This movement is other groups getting moved upside down. Getting Operations busy, shifting their activities left, previously in the cycle, and automating as many Ops tasks and activities as possible with tools like Puppet, or Chef, and Docker, among many others.
To move all this business-oriented product completed on their schedule, there is even extra use of task automation. To get a good impression of where DevOps is running — everything that must be automated has to be.
From builds using CI and test automation, we developed Agile. Test teams have been working with these tasks for a long period, but now more tasks and activities, basically Ops tasks: build promotion, building and maintaining environments, provisioning, monitoring — are all becoming automated. For Test teams, this means a lot.
Instead of the team dynamics, tools, and responsiveness to modification, this, of course, means larger and more intelligent test automation. How we consider test automation has to progress and grow. Its usage, and where to fit test automation and how this cycle affects our regular Development sprints is expanding the role of the test teams — basically, we have a lot to learn and a lot to modify.
To be DevOps and not DevFlops — first, we have to know what we are aiming for, why, goals and how we can best support the business. It’s a challenge. From acknowledge, to accepting, directing and defining where QA use into DevOps, the June Issue of LogiGear Magazine is supplied full of resources on how test teams should make the shift to Continuous Testing.