First the buzzword was ALM, then DevTest. Now it’s DevOps. But let’s not discount it just because it’s the nom-du-jour. We at Northwest Cadence say it often – Integrating your development processes with your operation process can result in increased value for your organization. How so? A healthy DevOps organization will likely see decreased release-cycle times and along with that, improved response times to production-related issues. But how do you get there?
First, you need to agree that keeping your Dev and Ops teams in silos is one of the big problems. The solution is to remove the walls whether operational or organizational. It’s not easy, but it’s necessary. Second, you need to invest in automation. Automation of builds, deployments, creation of environments, etc. Manual practices are time consuming, error inducing and expensive. Last, you should look at the tools you are using and find ways to integrate and unify. DevOps isn’t just a tools problem, of course. It’s a process and practices problem, BUT disparate and non-integrated toolsets will reduce agility and your ability to be lean.
As I mentioned, solving your tools problem won’t solve all your DevOps barriers, but it’s a start. If you are currently using Visual Studio and are considering using Azure, you and your DevOps team are in luck. You can use the Azure Tools for Visual Studio and the Azure SDK to enable deeper integration with Azure. If you are planning on jumping into Visual Studio 2015, there’s some keen DevOps functionality with the Azure SDK, including the Environments Hub which allows you to ‘easily’ deploy to environments as well as share environments between team members.
Of course, Visual Studio and Azure integration is only a small part of what a DevOps organization needs. If you would like to talk to use about your DevOps practices and how you can increase the value your are delivering to your organization, please contact us!
Checkout the information on the Azure SDK here.
There’s also good information on the Azure Tools here.