“I just write the code and throw it over the wall. It’s up to Ops to make it work.” When Devs care only about coding, Ops and customers suffer.
“It’s not my job to test code. If there’s a problem, talk to QA.” When Ops care only about stability, innovation and customers suffer.
DevOps represents cultural change. Whether it’s the change of resistant engineers that don’t want to be on-call or the change of Operations teams to have more empathy towards their counterparts writing code, to the willingness of executives to embrace a culture of automation, measurement and sharing.
Organizations must overcome the culture war to be able to approach the agility and productivity that organizations following a DevOps model gain. The faster they can get there, the faster these organizations can take the competitive edge away from traditional enterprises.
In most organizations, the mandate of a developer is merely to produce a piece of software that works – if it worked within an engineer’s development environment, then someone else must be able to make it work in production, right? Ideally, developers must care how secure their apps are, how hard they are to deploy, how hard they are to keep running, because their colleagues on the Ops side are typically paying the price for issues once the product is released to the public, not the developers who built it.
Having developers take part in the troubleshooting part of production can help to instill a deeper sense of craftsmanship and pride in their work, while also shedding light on how the application’s architecture interacts with the infrastructure it sits on. Additionally, when you set the expectation that everyone in the company will take part in the on-call process, you create a sense of interdependence and trust that can be lacking if only a small percentage of the team is forced to maintain uptime.
On April 30th, our CEO Todd Vernon will host a webinar panel that will be addressing this very topic. Joining Todd will be…
Kurt Bittner Principal Analyst Forrester Research Kurt Bittner is a leading expert on Agile and iterative software development approaches, including application life-cycle management (ALM). He focuses on the organizational and cultural shifts necessary to extract broader business value from software development processes.
Nick Goodman ** **Director of Platform Engineering at Bunchball Nick’s teams deliver Gamification solutions via a SaaS platform. As the Director of Platform Engineering, Nick oversees the software development and support of the Bunchball SaaS platform, which for the past year, has also included shifting Bunchball to a DevOps culture and building out a dedicated DevOps team.
Paul Beltrani TechOps at Onshape Paul’s previous roles include Director of Systems Engineering at Athenahealth, Inc., and Principal Architect at DataXu. Onshape is a startup that applies cloud, web and mobile technologies to CAD; Paul was brought on board to quickly mature the startup’s operations.
In this webinar we will look at:
- The current state of organizations - a separation of Devs and Ops
- The how of DevOps - DevOps is a culture, not a product
- The benefits of DevOps - happier customers
During the discussion, you will learn the benefits, and how to create a culture, of shared success between Dev and Ops teams from companies that have successfully made the transition - not only around mindset but also around processes.
Finally, we will answer the following questions to help you get started building a DevOps culture within your organization:
- Why change the status quo?
- How do I align two disparate groups?
- How do I remove the obstacles that separate Dev and Ops teams?
- Will customers see a difference if devs are on call?
- Can IT start to think differently?
Sign up for the webinar and find out why adding devs to the on-call rotation is a good idea for business!
All registrants will receive a complimentary copy of the Forrester Brief “Put Developers On The Front Lines of App Support” after the webinar.