The Doppler Quarterly Fall 2017 - Page 73

Score: 1.57 Collaboration Technology People Ownership Requirements Skills CI/CD Monitoring Innovation Scorecards ACME Typical Lean & Agile Eng. Practices Automation Governance Process Figure 3: DevOps Maturity Model Score* goal of this approach is to not let issues progress downstream, because it is much more expensive and time consuming to fix defects later in the lifecycle. DevOps Maturity After evaluating our client’s capabilities in the area of people, process, and technology we provide a maturity score. The score is a snapshot of the client’s current state of maturity. Next, we pro- vide a list of gaps in each area that shows the delta between the current state and the desired future state. Clients often want to start with a maturity of level 3 so that they can get to a consistent, secure, and reliable state for deploy- ments, while achieving a higher level of agility. The score provides us a place to begin the conversation, but where the rubber meets the road is in the details behind the score. We provide a list of gaps, in a roadmap format, and the recommendations for each gap. The number of gaps can be quite overwhelming, especially if a customer is early in their journey. But it is this roadmap that brings clients the most value. What bottlenecks should they work on first and in what order? How can they work on people, process, and technology changes concurrently? Too often we see clients only implement the technology recommendations and make little to no progress on the people and process recommendations. The end result is a suboptimal experience in the cloud and a missed opportunity to achieve the ROI that could be achieved by treating the cloud journey as a transformational project, as opposed to just a technology project. FALL 2017 | THE DOPPLER | 71