Getting Out of the 'DevOps' Way

Michael Vizard

Just about everybody agrees that the so-called "DevOps" process is fundamentally broken; it's just that nobody is quite sure what to do about it.

Arguably, there never was much of a formal DevOps process. It wasn't until the rise of agile development that IT organizations realized they needed a more structured approach to managing new releases and updates to applications that are now coming fast and furious. Previously, if there were a problem, they just told the developers to fix the problem sometime in the next couple of months, or they went out and acquired the gear needed to run the application as is. Now there is no time for that.

Unfortunately, developers and IT operations teams don't have much time for each other either. What's needed is an approach to DevOps that gives IT operations people visibility into the application development process and developers insight into the state of IT operations without requiring either group to fundamentally change the way they work.

According to Carl Landers, vice president of product marketing for Serena Software, that's the goal that Serena Software is trying to achieve with the launch this week of Orchestrated IT, a new platform for managing the DevOps process. Orchestrated IT not only automates many of the processes associated with rolling out a new application or update, Landers says it's designed to give all the parties with a vested interest more visibility into the overall process. That include business stakeholders, says Landers, who can now access dashboards to issue service requests and track the overall progress on any given project.


Orchestrated IT uses the data that Serena already has access to via its existing application and IT infrastructure management software. That information about the real-world status of production environments is fed into Orchestrated IT, which uses it to inform and automate various aspects of the application release cycle.

Orchestrated IT can either be invoked as a cloud service or as an on-premise application. While more application development is moving to the cloud each day, Landers says Serena wants to give customers the option of deploying a point of control for that process either in the cloud or on their own local systems.

In either scenario, the end goal should be to allow developers and IT operations to get out of each other's way. They obviously need each other to be successful. But that doesn't necessarily mean that they need to spend a lot of time actually talking to each other in order to achieve their respective goals.

Add Comment      Leave a comment on this blog post
Mar 18, 2012 7:07 AM TheManagement TheManagement  says:

Yeah people are a lot easier to manage if they don't talk to each other... until they need training and managers "don't have time for that."

Mar 18, 2012 8:19 AM Lowe Schmidt Lowe Schmidt  says:

Oh, a bought piece by a software company. First insult everyone then try and sell us stuff. Smart move, very smart move.

Mar 19, 2012 6:11 AM Service Orchestrator Service Orchestrator  says:

Looks to me like they just took the beginnings of DevOps process and replaced the culture with service-orchestration and a management scheme that can be prescribed as a methodology. Very consumable... but perhaps not the full spectrum of what should be. DevOps isn't broken, it's just a ride where you have to be a certain height to get on at this point in the beginning. Every kid grows up, some of us came up harder than others. That's kind of the difference between Dev and Ops or QA. Ops is pure scar tissue and maybe QA has a few scars. Beating down Dev is a good way to not get anything new for a while, if that's what people are into. Service-orchestration is new... it was developed by developers even though ops had the requirements.


Post a comment





(Maximum characters: 1200). You have 1200 characters left.




Subscribe to our Newsletters

Sign up now and get the best business technology insights direct to your inbox.