Step 2 to get started with DevOps: Assess where you are today
In my last blog post I defined what we want to achieve in our DevOps improvement initiative. Once that is done, we need to know where we are today. Sometimes it is difficult for my clients to assess on their own where everything is going well or otherwise. Most tend to know the biggest pains but not necessarily the why. This blog post outlines some guidelines for you to use when assessing your maturity to know where you should begin.
Where am I today?
In my recent paper on “Ado
What do you measure and currently achieve?
Most of my clients have some sort of measurements already in place for projects and teams. Their measures may be cost, resource or quality driven.
You can be sure that whatever your areas of measurement are, your team is sensitive to them and works toward keeping the results favorable. If not, then they probably get feedback quickly.
When you adopt DevOps it is a good practice to take the time to understand which measures are in place and can be used for improvement. Existing benchmarks can help you to judge the effects of an improvement. In step 1 I discussed the goal to “improve quality of distributed applications promoted from the testing environments.” For this goal you could consider which measure you would use to reflect the impact of improving quality (requirements, coding, design and so on).
What don’t you measure, but should to improve?
For those who need improvement in areas where you don’t measure today, first consider how to determine success. This may take a little extra time but will pay off in the end.
Going back to the quality example, if you do not include a root cause category for “environment” but are planning to improve how you provision or configure middleware, you may want to consider how you might measure the expected change in defect rate.
Do your team members agree with these findings?
As you develop your assessment of your current state, run it by the key experts from different practice areas and organizations. Get their concurrence with the findings and measures. Their understanding of what is going on under the hood can make a big difference in your next steps when your prioritize changes. But we’ll discuss prioritizing in my next blog post.
Are you thinking about implementing DevOps but trying to assess where you are today? Check out IBM’