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.
19 MARCH, 2020 by Michiel Mulders SRE vs DevOps: Friends or Foes? Nowadays, there’s a lack of clarity about the difference between site reliability engineering (SRE) and development and operations (DevOps). There’s definitely an overlap between the roles, even though...
06 MARCH, 2020 by Arnab Roy Chowdhury Top 10 SRE Practices Do you know what the key to a successful website is? Well, you’re probably going to say that it’s quality coding. However, today, there’s one more aspect that we should consider. That’s reliability. There are...
20 FEBRUARY, 2020 by Arnab Row Chowdhury Technically, the world today has advanced to a level we never could’ve imagined a few years ago. What do you think made it possible? We now understand complexities. And how do you think that became possible? Literacy! Since...
14 FEBRUARY, 2020 by Michiel Mulders A site reliability engineer loves optimizing inefficient processes but also needs coding skills. He or she must have a deep understanding of the software to optimize processes. Therefore, we can say an SRE contributes directly to...
07 February, 2020 by Arnab Roy Chowdhury Do you remember what Uncle Ben said to young Peter Parker? “With great power comes great responsibility.” The same applies to companies. At present, businesses hold a huge amount of data—not only the data of a company but also...
17 JANUARY, 2020 by Sylvia Fronczak Site reliability engineering (SRE) uses techniques and approaches from software engineering to tackle reliability problems with a team’s operations and a site’s infrastructure. Knowing the history of SRE and understanding which...