100% Agile within a Year – The DevOps Cube

25
SEPTEMBER 2017 by Niall Crawford
An interesting article I spotted on LinkedIn this week:
  • [Bank] to be “100 per cent Agile” within a year, says senior coach
Interesting for a few reasons, one – the post was quickly removed after receiving a battering in the comments section and across general social media and secondly because these “agile at scale” comments are a pet “bug-bear” of mine.
Saying that however, I probably must also assume that the excitable author may have “partially” miscommunicated the intended message of the “agile thought leader” and thus why the article was quickly swept under the carpet. Nevertheless, it did get me thinking. 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
Companies tend to be federated, by Business Unit or Platform and of course teams. This of course has certain benefits, however, it also means “mileage” can vary. Some teams have good leaders & smart engineers, other poorer divisions less so.
  1. Measuring agile is difficult.
Counting the number of agile coaches is not a realistic method and organizations rarely have the necessary statistics (past baseline information or accurate real-time statistics) to demonstrate they have accelerated delivery timelines, increased change volumes and continue to provide quality. With this objective in mind, I set a challenge for the team to come up with a solution, using our own Enov8 Platform, that our clients might use as a method, in part at least, to measure their IT maturity & agility. The result after some brain storming was the “DevOps Cube”.
DevOps Cube
An approach based on understanding the organization is built upon IT Systems & Platforms. Each system is made up of building blocks that span across:
  • IT Environment Tiers i.e. infrastructure, applications & data
  • IT Environment Operations e.g. build, deploy, test (& maybe secure).
They also have different maturity levels from Chaos to Defined to Automated to Self-Service.
Using this method of measurement, which is already captured with the enov8 platform, an organization can determine at a granular level whether a system instance has CICD (Continuous Integration / Continuous Delivery) capabilities and review it at a more holistic level e.g. by Platform, Business Unit or Enterprise.
Enov8 will be providing the DevOps Cube with their Environment & Release Management solutions. Request a demo, or contact us for more information about the enov8 platform.

Relevant Articles

Data Cloning (aka Virtualization) – An Introduction

MAR, 2023 by Gourav Bais. Author Gourav Bais. Edited by Jane Temov This post was written by Gourav Bais.Gourav is an applied machine learning engineer skilled in computer vision/deep learning pipeline development, creating machine learning models, retraining systems,...

What is Data Lineage – A CI/CD Example

MAR, 2023 by Niall Crawford.   Author 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....

Which Release Cycle is Better: Monthly or Quarterly?

MAR, 2023 by Andrew Walker   Author Andrew Walker Andrew Walker is a software architect with 10+ years of experience. Andrew is passionate about his craft, and he loves using his skills to design enterprise solutions for Enov8, in the areas of IT Environments,...

Process Improvement Strategies for Release Management

MAR, 2023 by Andrew Walker.   Author Andrew Walker Andrew Walker is a software architect with 10+ years of experience. Andrew is passionate about his craft, and he loves using his skills to design enterprise solutions for Enov8, in the areas of IT Environments,...