Is Enterprise DevOps Overly Ambitious?

The year is 2019 and I had the great pleasure of working on a full stack of DevOps practice, people training and technology implementation over the past few years. With that experience alongside that of an esteemed colleague at work, we decided to write an article on the theme: "Is Enterprise DevOps Overly Ambitious" and presented to a few clients and at a community event.

Here's a quick synopsis of some of the points that we unpacked as part of a great debate:

1. Enterprise DevOps is not a project, it's an enterprise's cultural and architectural journey.
2. Automation does not trump human intervention and processes. We still need to have enterprise change management for the latter points.
3. Email with links does not constitute 'just enough' training and change management 101.
4. Metrics are key to keep oversight and insight of the overall value stream delivery. DevOps doesn't mean 100% transparency without proper planning.
5. Quality doesn't happen automagically. It requires practice, process and human intervention.
6. Finance and HR aspects of Enterprise DevOps are very important links of your value proposition. Managing Opex vs Capex for DevOps as well as change of roles is a critical part of adoption success criteria.

Should you be interested to learn more on this theme or would be interested to book for a presentation, please do get in touch.

I leave you with my own conclusion: Enterprise DevOps requires one to dig deep and understand the true practice and modus operandi, not get sucked in buzzwords and be practical in order to adapt the concepts in the symantics of your enterprise and make it a success.