Select Page

Sand Castles and DevOps at Scale

07
FEBRUARY, 2018

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.

Opinion

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.


Five Practices

As a way of preparing for a DevOps at scale capability, here are five practices to promote.

  1. Understand what your End-to-End Environments 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.

  1. 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.

  1. 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.

  1. Orchestrate enterprise release activity

Avoid common “release issues”, “deployment delays” and “rollbacks” 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.

  1. 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


Solutioning

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.

Enov8 EcoSystem is the worlds leading IT Enterprise Intelligence platform.

EcoSystem is a fully configurable and easily integratable solution that comes with out of the box “enterprise management” functions that support IT & Test Environment Management, Release Management, Data Management, IT Operations Management, Configuration Management & Service Management.

Niall Crawford

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.

Relevant Articles

Supporting Privacy Regulations in Non-Production

18 SEPTEMBER 2020 by Arnab Chowdhury Every aspect of our daily lives involves the usage of data. Be it our social media, banking account, or even while using an e-commerce site, we use data everywhere. This data may range from our names and contact information to our...

What Makes a Good Enterprise Release Manager?

09 SEPTEMBER, 2020 by Michiel Mulders Do you want your company to scale efficiently? Look for an enterprise release manager (ERM). An ERM protects and manages the movements of releases in multiple environments. This includes build, test, and production environments....

What Is Data Masking and How Do We Do It?

04 AUGUST, 2020 by Michiel Mulders According to the 2019 IBM Data Breach report, the average data breach in 2019 cost 3.92 million USD. Businesses in certain industries, such as healthcare, suffer more substantial losses—6.45 million USD on average. As the amount of...

What is and why have a Release Calendar?

13 JULY, 2020 by Eric Boersma Every project manager in the world shares a similar stress. They’re working on something important, and a key stakeholder sticks their head around the corner. They ask a small, innocent question. “When are we going to release that...

What is and why have a Test Environment Booking Form?

01 JULY, 2020 by Diego Gavilanes Ever since the dawn of time, test environments have been left for the end, which is a headache for the testing team. They might be ready to start testing but can’t because there’s no test environment. And often, the department in...

Data Literacy and GDPR (Know Your Risk)

29 JUNE, 2020 by Carlos Schults In today’s post, we’ll discuss data literacy and its relevance in the context of GDPR. We start by defining data literacy and giving a brief overview of GDPR. Then we proceed to explain some of the challenges organizations might face...