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 AUGUST, 2019 by Jane Temov So, you’ve been asked to write a “Test Environment Management Plan”? Or perhaps you just want to write a plan to baseline your current non-production processes, outline future test environment strategy and/or educate those around you. *...
02 AUGUST, 2019 by Eric Olsson Preamble Software is buggy. It's a bold claim, I know. Sarcasm aside, the battle to keep your applications up and running is ongoing. Wouldn't it be nice if you had a way to eliminate an entire class of bugs from your application?...
15 JULY, 2019 by Peter Morlion Martin Fowler AntiPattern "An antipattern is a solution that initially looks like an attractive road lined with flowers... but further on leads you into a maze filled with monsters." Since the dawn of computers, we’ve always had to...
26 June, 2019 by Justin Reynolds Gone are the days of monolithic software applications. In today’s microservices-and-continuous-integration driven world, where apps run in hybrid cloud environments and users engage with them on any device and on any underlying...
03 JULY, 2019 by Justin Reynolds Even since the agile manifesto was published in 2001, software development has never been the same. In a pre-agile world, software was released in monolithic packages every year or every two years. The agile approach to development...
20 MAY, 2019 by Mark Henke It’s a great step when teams deliberately manage their deployments instead of treating them as second-class citizens to writing code. But there are many pitfalls to managing deployments effectively. Many things lurk, waiting to trip us up....