| | JUNE 20189CIOReview"It is necessary to move mindsets to think about different ways to solve DevOps problems"metric comes into play. By providing teams with this measure, broken into process times for development and testing and wait times as noted above, they can then determine what counter-measures or continuous improvement initiatives are needed to accelerate their delivery capability.Culture"Culture eats Strategy for Breakfast" ­ Peter Drucker Cultural changes are needed to empower teams to have more self-service and control over their delivery journey. A key cultural component is to achieve a balance between ensuring a capability and the underlying technology can be supported for the entire enterprise while still allowing teams to be empowered to use it in the way that best suits them to serve their business. A good example of this relates to deployment. In the past, the model might have been to centrally govern and control how deployments were done. This created several problems. It meant that teams which needed more flexibility would be motivated to find ways outside of the tooling to do what they wanted. These types of local optimizations created variations which increased waste and inefficiency. A second problem was that the team owning the tool became a bottleneck for any type of change needed for a specific team's configuration. This added an SLA to the process which increased the delivery lead time.A third problem was that any technology changes were evaluated from the basis of comparing tool `A' vs tool `B'. This results in decisions primarily focused on financial costs of the tool rather than how the tool impacted the ability of teams to delivery more quickly and efficiently. The evaluation needs to be based on what value is added to the integrated delivery pipeline supporting the value stream. In some cases, there were actually disincentives built into how tool usage was internally charged back to the teams using them which incented the team to utilize less of an automated tool to reduce the charge-back and resulted in resorting to more inefficient manual activities.These are the types of true cultural issues that have to be addressed in order to be successful at not only reducing lead time but creating a more efficient delivery value stream and underlying technology foundation that reduces overall costs and improves quality.Moving MindsetsAs we continue our DevOps journeys, it's necessary to move mindsets to think about different ways to solve these problems. Everyone in the company needs to think about how they are supporting the goal of being more responsive to the business needs. Reducing lead time and deploying more frequently can't just be the focus of the IT delivery teams. Optimizing the delivery value stream has to become the focus of the entire organization.
< Page 8 | Page 10 >