A key part of your DevOps programme, and instrumental in its success, is how DevOps and your applications are measured. If this measurement is done well, it will provide accurate ROI, help you to manage progress towards your DevOps goals, and be a great help in evangelising DevOps success.
Once the big decision has been made to go for DevOps in your organization (or at least give it a go), what do you do next? Below are my suggestions for things which should be considered at this early stage if you want to get started with a successful DevOps programme.
Following on from my previous post entitled 7 Steps to Start your DevOps Initiative, I thought I’d talk a bit about DevOps in the long term. Something which can easily be missed when on the DevOps journey is how to keep the momentum and make sure that good DevOps principles are not lost after the initial driving phase.
Being in software testing for many years now, I feel that one thing that has never changed is IT managers always being in a position to justify the investment of test automation or any technical enablers to improve the testing function within their organisation. I think this is mainly due to difficulty in proving the ROI for testing.
This blog follows on from last week’s Seven Steps to Start Your DevOps Initiative – part 1. The paper “Seven Steps to Start Your DevOps Initiative” by Ronni Colville (2014) lists 7 key recommendations for successfully implementing DevOps. Below I continue my discussion and share my insights for steps 5 – 7.
I attended a DevOps Connect breakfast briefing at The Royal Exchange on Wednesday 4th February 2015. The briefing, run by Ranger4 and DevOps.com, was centred around a Gartner paper released in 2014 called Seven Steps to Start Your DevOps Initiative by Ronni Colville. This paper lists 7 key recommendations for successfully implementing DevOps. In this post I discuss my insights for each step, based on my experience as well as discussions triggered from this breakfast briefing.