The separation of the operations and development roles hinders communication, fosters resentment and undermines trust – all of which results in a slower software delivery across the business. This is why many organizations are now merging the roles, implementing DevOps in an attempt to free themselves of these shackles and speed up their software delivery cycles.
DevOps has become the IT word of the moment in part because it just intuitively 'makes sense' to decision makers. After all, what's not to like about faster software delivery, higher quality, and a more cooperative work force?
However, like many seemingly simple things, behind the scenes implementing DevOps can be anything but straightforward. Combining the two roles can cause serious disruption, and before embarking on DevOps just because everyone else is doing it, IT leaders need to keep a cool head, to take a step back and ask themselves "Why are we doing this? What's involved? Is it really for us?".
Other questions will emerge when the decision to pursue DevOps has been taken: "How can we build a DevOps culture, emphasizing the win-win scenario when those involved fear change? What's the best place to start and how do I take people with me? What do I need to measure and what does success look like?"
Later, decisions will need to be taken about the role of Agile, continuous delivery vs. continuous deployment, the extent of automation, traditional vs specialized toolsets, and the rest.
DevOps is a significant development in the way that all types of companies operate - because companies in all sectors now develop their own software - but it is still new to most and so it is important to start the journey on the right path.
Join our expert panelists for this on-demand web seminar during which we will be fielding your questions on how to build a DevOps team that will really make a difference to your company.