DevOps Ticket Reduction
A reduction in DevOps tickets not only drives IT efficiency, but also creates a cultural shift where teams look forward to rapidly achieving accomplishments. Business stakeholders operate in an agile environment where no change request is too small, and rapidly testing business ideas is the new normal.
As a techie, I like to focus on the technology and IT process side of DevOps; bouncing around terms like ‘infrastructure as code’, ‘automated provisioning’, ‘continuous deployment’, and ‘continuous integration’. The value-prop is self-evident to me and many of my peers. Yet, for us to change corporate culture and rally around a New IT Plan, the main message focus must not be ’DevOps for DevOps Itself’, but to create a Responsive IT team that changes business-IT dynamics and accelerates business agility.
DevOps is not about ‘creating a better ALM’, but about working together as a single team, reducing wait times, automating repetitious tasks, and accelerating business innovation iterations. While the ‘NoOps‘ model is subject to confusion and derision, reducing manual activity and operation desk tickets is a straightforward goal.
Define infrastructure as code, automate manual actions, and create self-service interfaces that take the operator out of the middle. Teams usually invest a significant amount of work to build a more agile, self-service environment, or they can choose a ready-made DevOps PaaS that can be configured to match their workflow stages, gates, approval processes, and infrastructure templates.
Teams can measure progress by tracking the reduction in DevOps tickets, shorter ticket close average, and increased solution iteration count.Recommended Reading
(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)