From the Blogosphere
Will 2017 Be the Year of DevOps NoOps? | @DevOpsSummit #Agile #DevOps #ContinuousDelivery
With DevOps for digital natives evolving to NoOps, this blog tells you what established companies like yours must do to compete
By: Automic Blog
Apr. 7, 2017 05:00 PM
Will 2017 Be the Year of DevOps NoOps?
If DevOps continues on the same trajectory into 2017 as it has been on for the past few years, specialized Ops teams could quickly become redundant. Instead, DevOps for digital companies will evolve to require only developers who nurture their own code into production. So how do established companies like yours keep up with this level of agility when you rely on a combination of legacy and digital apps? Read on to find out.
NoOps for Start-Ups?
DevOps means dev and ops surpass merely working closer together; they reach into each other's disciplines and learn. This leads to a cross-pollination of skillsets, meaning everyone understands the whole app lifecycle better and where their role sits within in. This idea is nothing new and should be encouraged in any profession, whether IT, medicine, law or anything else.
If DevOps continues to blur the lines between the two disciplines, then ops practices could all be performed by careful developers. This will add agility by reducing the need for cooperation; DevOps is encapsulated in one staff member.
For companies that do grow from scratch in today's DevOps world, the need to disrupt and be agile in development means that specialized ops staff should only be added when absolutely necessary. A more agile solution would be to hire development staff that care about how their code is deployed.
When Are Dedicated Ops Really Necessary?
What is important in this situation is not simply to hire an ops person to take care of all this work. Ideally they would do a minimal amount of actual ops work, and instead act as mentors for devs looking to learn the ops side of DevOps, which in theory should be all of them. For this reason it's important to hire someone whose skillset varies from that possessed by the team already, to bring something new to the company and spread that knowledge. Bring a dev a fish and he will eat for a day, but bring him a fishing rod and...erm, well you know where I'm going with that!
But What About Legacy Organizations?
For established enterprises that want to adopt a NoOps model, how do they do this in practice? Just sack all their ops staff one day? In an international, 24/7 world with Continuous Delivery of applications becoming more widespread, downtime is almost unheard of. So reverse engineering a NoOps scenario without significant downtime would be difficult.
However, your company must adapt to compete with the level of agility offered by your digital competition. Reputation and history have been overtaken by functionality and apps as the number one consumer requirement, and a reputation built over decades can be quickly tarnished and forgotten if that company fails to digitally transform. Just ask Blockbuster.
The Answer is AgileOps
Typically, these days the development part is now project/pipeline driven: CI -> QA -> provision -> deploy, but then it runs into ops, which is still largely interrupt driven, and ops can't keep pace. They find it impossible to keep to a set plan as they must respond to all the requests coming in from other teams. They're fighting fires every day and cannot find the time to think make practices more agile.
So how we can help make ops agile?
Consistent Continuous Delivery Automation
Consistent automation transcends employees, who can move jobs or department etc. The system stays in place to give business continuity; it is repeatable. So when you on-board new employees they have a standardized working process to follow, rather than trying to figure out what is supposed to happen from information aggregated from multiple colleagues. You don't lose agility from complex, ad hoc handovers.
If in 2017 you must compete with digital natives capable of working without dedicated ops teams, then your ops need to be as agile as possible.
Latest AJAXWorld RIA Stories
Subscribe to the World's Most Powerful Newsletters
Subscribe to Our Rss Feeds & Get Your SYS-CON News Live!
SYS-CON Featured Whitepapers
Most Read This Week