Sand Castles and DevOps at Scale
by Niall Crawford
“DevOps & DevOps at Scale is a little bit like comparing the building of Sand Castles on a Beach to Town Planning”.
A Bit of History
The phrase DevOps first appeared back in 2008 at an agile conference in Toronto. And in a nutshell (& courtesy of Wikipedia) can be defined as a software engineering culture and practice that aims at unifying software development (Dev) and software operation (Ops). Ultimately with the intent of reducing the time between committing a change to a system and the change being placed into normal production, while ensuring high quality.
Well, that’s the theory at least, and to be fair “mileage” somewhat varies.
+ The success of DevOps is invariably dependent on the quality of the individuals & the team.
And in my opinion, the biggest challenge in most organizations (particularly the larger ones) is few changes touch an individual system. In fact, it is probably quite the contrary, typically an IT change impacts many systems, processes & services and crosses many technology teams, divisions and various IT Environment tiers e.g. applications, data & infrastructure tiers.
+ In today’s Complex IT Environments, few Systems or components are islands.
And here lies in the issue.
+ DevOps encourages a culture of “System” or “Team Thinking”.
However, effective DevOps at scale, requires us to think at a broader “Enterprise” level.
An Analogy: DevOps & DevOps at Scale
+ It is a little bit like comparing the building of Sand Castles on a Beach to Town Planning.
Yes, it might be fun & you might build a damn good sandcastle (or CICD capability) but unfortunately some of your sister teams will fall short of the mark, and ultimately the whole task of integrating is going to slow down and the so called “Release Train” will grind to a sudden halt.
Delivering DevOps at Scale
Organizations cannot expect DevOps teams, which are naturally focused on discrete systems or atomic tasks, to effectively manage and deliver a solution at scale unless there is some form of enterprise harness that ensures all the moving parts can be effectively orchestrated.
+ DevOps is more than simple Code, Build, Test, Package, Release, Configure & Monitor.
Ultimately, DevOps at Scale is about resolving the classical cross-system orchestration challenges experienced today and providing an approach, preferably a complimentary & non-obtrusive approach, that overarches existing DevOps methods and ensure the release train wheels are greased and your delivery is streamlined.
As a way of preparing for a DevOps at scale capability, here are five practices to promote.
- Understand what your End-to-End Environment look like.
Look beyond your systems & model the End to End IT & Test Environments they live in. Understand them intrinsically i.e. map your components, dependencies, interfaces, business relationships, processes and supporting operations.
- Shift your release / operational planning & coordination left
Avoid the ongoing issues around System not being fit for purpose and/or contention. Capture project & portfolio demand as early as possible and establish effective notification & transparency methods to ensure readiness and awareness.
- Don’t neglect the data
How often do you see the CICD solutions fail as nobody bothered about the data?
In addition to streamlining Application & Infrastructure tasks, invest in data. Automate key data tasks like ETL (Extract, Transform & Load) and/or Fabrication and ensure the automation methods are “cross system aware”, thus ensuring E2E integrity.
- Orchestrate enterprise release activity
Avoid common “release issues”, “deployment delays” and “roll backs” by adopting an “Enterprise Release Management” (ERM) strategy. A strategy that promotes prioritisation of change, alignment of cross system release activities and promotes consistent and repeatable operations.
- Promote higher levels of “Enterprise Intelligence”
System metrics are fine although off little use to executive decision makers or your CIO. Start capturing & reporting on “Enterprise Metrics” i.e. metrics that allow the senior executives to see the “forest from the trees”. Examples may include Team Performance, Compliance, Automation & Innovation
Enov8 provides a complete platform for addressing organisations DevOps at scale requirements. Providing advanced “out of the box” IT & Test Environment Management and Release Management capabilities, the enov8 platform uplifts enterprise transparency, command and ultimately control.
Innovate with Enov8
If you are interested in learning more about IT & Test Environment Management and IT Release Management, contact us about EcoSystem.
Ecosystem is a fully configurable and easily integratable solution that comes with out of the box “enterprise management” functions that support i.e. IT & Test Environment Management, Release Management, Data Management, IT Operations Management, Configuration Management & Service Management.
Niall is the Co-Founder and CIO of Enov8. He has 25 years of experience working across the IT industry from Software Engineering, Architecture, IT & Test Environment Management and Executive Leadership. Niall has worked with, and advised, many global organisations covering verticals like Banking, Defence, Telecom and Information Technology Services.
21 FEBRUARY, 2018 by Niall Crawford I am continually 'un-amazed' when I go into large organizations and look at their 'DevOps' strategy. At a team level, it's invariably no different to what we were doing back in the late 90’s (perhaps with exception to some of the...
The intention of environment synthetics is to provide ‘high-level of confidence’ applications (your system instances e.g. UAT Home Loan System) and their underlying component services…
This year’s world quality report (2018) has once again identified Test Environment Management as a major challenge for Agile Development & Testing. Key statistical insights from this report included…
A key responsibility of any CIO is to find the correct technology partners to deliver IT services. Ideally services that will be delivered: Better, Faster, or at the very least Cheaper. A process that involves RFPs, Presentations, Strategy Workshops…
13 OCTOBER, 2017 by Niall Crawford According to Wikipedia, Enterprise Release Management (ERM) can be defined as: A multi-disciplinary IT governance framework for managing software delivery & software change across multiple departments in a large organization. ERM...
How could a large company, like a bank, be 100% agile? And how could they prove it?
I see two fundamental challenges or truisms: 1. Companies are federated 2. Measuring Agile is Difficult