100% Agile within a Year – The DevOps Cube
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:
- 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.
- 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”.
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.
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...
Test Environments Anti Patterns
A common term used in the world of Software Development is the concept of Anti-Patterns. An Anti-Pattern is basically a commonly occurring approach to a problem or task that generates decidedly negative consequences…
DevOps is a set of practices that automates the processes between software development and IT teams, allowing them to build, test, and release software faster and more reliably. The concept of DevOps is based on collaboration between teams that historically functioned in relative silos…
Reduce Test Environment Downtime – In this blog article, we will discuss about how test environment managers can minimise environment downtime and how enov8 can help in achieving this dream.
Before starting this topic on importance of Release Gates, lets understand – what is a release gate?
A Release Gate can be defined as a milestone or health indicator of a release at that very point in time…
Metrics for your Non Production and Test Environments. Ever wondered how you should measure your Test Environment capability? Well it can be hard without a platform like Enov8 Ecosystem, a solution that allows you to bring all your…