While working as a software quality manager at a large company within the Netherlands, we started working on the repeatability and testability of our Linux platforms. We wanted to be able to deliver hight quality Linux platforms and deliver them fast. We believe that both of these abilities are key to achieving that goal. In the next month, I will post a series of blog posts on our experiences.

In the last couple of blog posts, I’ve talked about how to describe how mature you are in your ability to do continuous deployment. This blog post introduced a way to visualise the maturity. In this blog post I described the area’s of interest on the x-scale of the graph. While in the last blog post I described the levels of maturity on the y-scale. That’s all nice, but how do you use these ingredients to assess YOUR continuous deployment maturity? In this blog post, I will introduce some criteria.

In my last blog post, I described the main area’s of interest to work on to get faster and easier deployments. For every area, the level of maturity may be different. In this blog post, I will dive deeper in the levels of maturity and what they mean.

In my last blog post, I showed a way to visualize the level of maturity for the six interest area’s of continuous delivery. In this blog post, I will dig deeper into what the areas of interest are.

Looking around the Internet, you see more and more companies starting to do multiple deployments per day. There are the stories of Facebook deploying multiple times per day. The stories of The Guardian and many more. If you want to go down that path, it really helps having a way of visualizing where you are, and where you want to go to. This helps the discussion with the stakeholders and gets things going. In this blog post, I will demonstrate a way to do just that.