Have you tried NoOps yet?
It’s strange how putting the same letters in lower case and capitalized next to each other distorts the look of a word.
NoOps doesn’t look like Noops.
You’d never pronounce it in a way that rhymes with loops. Your brain autocorrects and creates the space the capitalization demands - and it reads No Ops.
And that’s a shame. Because loops are exactly what your Dev team is going around in.
Build something. Ask Ops to deploy it. Ask Testing to test it. Wait. Review the feedback. Fix something. Repeat until fade.
The hand-off chain goes something like this...
Which is unfortunate. Because if you could remove Ops, the hand-off chain would be more like this...
Which would be much, much quicker. And cheaper.
I recently read a Forrester article dating back to 2011. It raised the notion that while DevOps is an admirable principle, NoOps should be a more ambitious target of IT delivery. So, rather than improving Dev and Ops working practices, the ultimate goal should be to remove Ops all together so that Dev can do its own thing unencumbered.
Forrester defines NoOps as "The goal of completely automating the deployment, monitoring, and management of applications and the infrastructure on which they run."
Personally, I think the whole monitoring and management is something that Dev should steer clear of. Sure, they need to see results and understand the capacity and performance implications of their efforts. But monitoring and managing production infrastructure need a ‘line’. There needs to be some form of architectural design authority between a developer wanting something and getting something.
Want more capacity?
The first response should be ‘why?’ - not ‘fill your boots’.
But Deployment automation?
Go for it.
As long as your Dev team can be confident that what’s being deployed is known. As long as the deployment has been approved. And as long as it can be reversed without downtime. Then why not? NoOps is the right way to increase development cadence.
Next, automate testing and the provisioning of production-like test environments and you have a near-real-time Dev process with no dependency on external resources. That’s when Agile moves from being a methodology to a reality.
But let me stress something...
NoOps is only one letter away from being the last thing you want going through your mind when you automatically deploy something to production that wasn’t what you thought you'd tested.
If you can’t guarantee that your automated deployment process and clever testing automation method are on-point, instead of DevOps or NoOps, you’re simply going to be thinking...
ActiveControl takes NoOps a step further - OneStep back-out also gives you No oOps.
To learn more about back-out, download the ActiveControl feature sheet now.