Creating a Feedback Loop
DevOps in itself is a continuous improvement in ways of working. It is of utmost importance to enable feedback mechanism
- From a Business point of view, constant feed back on Right first time and on improvement of product launches.
- From the DevOps teams side, efficiency brought in by tools and also further streamlining of processes
- From the operations side, continuous automation of anything that is repeatable and more movement efforts spent on DevOps activities
- From teams for changes, toolsets and processes being introduced to them
- From stakeholders, sponsors on the effect on Opex reduction, plus experience with the end customer is post inducing entire ownership to a single team.
- From IT all together, in terms of how automations and optimization is helping them
With this, we can develop a good feedback and communication mechanism to work on and improve on those to cultivate a stable IT setup.
Gradually, we will see a decline in manual efforts being spent on most operations tasks and almost everything being automated. This would eventually lead us to our nirvana stage of “No-Ops” support at all; thus marking the successful completion of realistic functional DevOps and moving toward End State.
An initial step toward realistic DevOps culture can be stated as success, once the below parameters are showing improvements:
- Faster release and deployment
- Right first time and speed in incidentresolutions
- Improvement in automation levels
- Maturity in Knowledge Management
- Processes getting leaner and executed withminimal exceptions
Once this reaches acceptable KPI levels, the organization can move forward to full-fledged DevOps with the entire automation suite in place and then toward the final journey of No-Ops.