|By Jason Bloomberg||
|August 1, 2014 08:45 AM EDT||
Want to know a secret? I loathe the phrase Digital Transformation. Not only is the word Digital silly and misleading, but Transformation ain’t much better. The mere act of naming a business initiative Digital Transformation suggests to people that once the transformation is complete, we’ll be done. Look at us! We’re Digitally Transformed!
Hogwash. A single transformation is better than nothing, but what we really want is the ability to transform our business as needed. Furthermore, we need to be agile with our transformation initiative itself. The last thing we want is to institute, say, a three-year transformation effort, only to find at the end of the three years that the world changed a year into the initiative, rendering it a useless waste of money and effort.
So, who are the right people in the organization to address this sorry state of affairs? Driving the change needed to make our organizations more successful at such ongoing transformation should ideally fall to the Enterprise Architects. Unfortunately, the way Enterprise Architecture (EA) is done today falls well short of this mark.
Traditional EA starts with documenting the initial state of an enterprise. Then Enterprise Architects document the final state as required by the business. Finally, they help the organization plan how to get from one state to the other.
There are only three things wrong with this way to think about EA: The initial state. The final state. And yes, the plan to get from one to the other. It’s no wonder most organizations who were fool enough to sink money into EA believe EA is completely broken. Even EAs think EA is broken, and they do it for a living!
But no matter how fun it is to bemoan this sorry state of affairs, this Cortex must help point the direction to a better way of thinking about – and doing – Enterprise Architecture. The success of any Digital Transformation effort hangs in the balance.
What’s Wrong with Point A to Point B?
It seems so intuitive that the way to solve a problem is first, understand the problem, second, understand the solution, and third, solve the problem. Unfortunately, many EA initiatives don’t get past step one. Documenting the initial state of an enterprise – or even simply documenting the initial state of an enterprise’s IT environment, which is usually where EAs focus their efforts – is an exercise in futility. There are simply way too many bits and pieces, moving parts made of people and technology, for such an activity to ever complete, let alone provide sufficient detail to add clarity to the situation. Remember, the organization is always in flux. Even if you could take a snapshot of everything, it would be out of date a moment later.
What about the final state? That’s the nirvana situation where all your problems are solved, right? OK, raise your hand if there was ever a time in your career where all the problems were solved, all the bugs were fixed, all the projects were complete. Anybody? Sounds rather unrealistic, wouldn’t you say? Even if you narrow your scope to a single aspect of your business or even a single project, there is nothing final about a final state, if you could even refer to such an implausible scenario as a state, which is asking a lot. Remember, everything is connected to everything else, and everything is always changing. The notion of a “final state” is an unrealistic simplification that misleads people into thinking the approach they’re taking will actually solve problems.
Very well, let’s say you’ve still reading, in spite of thinking my comments on initial and final state are a bunch of hogwash. Certainly, you may ask, the EAs can at least concoct some kind of plan for getting from point A to point B? Sorry to disappoint. If what you mean by a “plan” is a description of the steps you must take that you can put together before you take those steps, then no. You’ll never come up with such a plan that ends up having any relationship to reality by even the halfway mark. There are simply too many unknowns, and too many things can change along the way.
Moving Up a Level
The core problem with this traditional approach to architecture is that it is simply too literal. It deals with things as they are and things as you desire them to be, without dealing with the fact that everything is subject to change. But the good news is, we architects have a wonderful tool in our box of tricks for dealing with excess literalness: the tool of abstraction. If we move up a level of abstraction, we’re no longer thinking about initial and final state. Instead, we’re thinking about moving from being less agile to being more agile.
Literal-minded thinkers (and I know you’re out there) will be protesting at this point that “being less agile” is our initial state and “being more agile” is our final state, so we’re just playing word games. And if you squint and hold your nose, there is a minuscule portion of truth in that overly literal perspective – but you’re missing the point here. “Being less agile” describes any number of possible initial states we may find ourselves in, and “being more agile” means being able to deal with change better, no matter which state we started at or where we happened to end up.
Put another way: moving from A to B describes a change (or actually, a set of changes) in the organization. Moving from less agile to more agile describes a change in how the organization deals with change, from being less able to deal with change to being more able to deal with change. In other words, we’re now thinking at the Meta level. We’re not doing architecture any more, oh no. We’re doing meta-architecture: we’re architecting our architecture.
Introducing the Bloomberg Agile Architecture™ Maturity Metamodel
Time to put some meat on these bones. As I’ve explained before, the Bloomberg Agile Architecture (BAA) Technique is a particular approach to implementing EA that is business agility driven. It’s not a framework you need to subtract from but a technique that complements other architectural efforts. Today I’m rolling out a core BAA artifact: the BAA Maturity Metamodel.
Try as I might, I couldn’t fit the entire chart into this article, so instead, I’ve linked to a pdf version of the Metamodel. Click here or the image below to download the pdf.
Unfortunately, there isn’t room in this Cortex to fully explain the BAA Maturity Metamodel (for that, take one of our classes to learn all the details, or drop me a line). But there is room here for a few of the highlights.
First, notice the four levels: Chaotic State, First-Gen SOA/Centralized, Next-Gen SOA/Cloud-Centric, and Agile Architecture. These designations refer to the organization’s context for architecture as it matures from less agile to more agile. In other words, it maps how your architecture is evolving – and thus the chart represents an aspect of your meta-architecture.
Second, note the twelve dimensions (rows), sorted neatly into four areas: Organization, Process, Information, and Technology. This organization of dimensions is more a matter of convenience than anything else. Feel free to rearrange the dimensions as you see fit.
In fact, feel free to change anything in the metamodel you see fit, based upon your situation – and always be willing to change it as your architecture evolves. Remember, there are two sides to being agile: the core driver of business agility (increasing in the metamodel from left to right) and the fact that BAA is Agile in approach (in other words, generally follows the principles of the Agile Manifesto). And as ye old Manifesto sayeth, thou shalt respond to change over following a plan. Even if the plan is to be Agile!
Finally, never forget what this diagram is for. It’s for helping architects coordinate change across the organization as driven by business needs. The metamodel – or any other aspect of the architecture – never tells the business what it should do. In the immortal words of a well-known sage: “business needs drive the architecture, and architecture drives the technology. Never let technology drive the architecture or the architecture drive the business.” Couldn’t have said it better myself.
The Intellyx Take
I know that many of you who took the time to download the Maturity Metamodel will have many questions about it – and over time, I’ll get to the answers. But just to whet your appetite a wee bit further, let’s take a moment to discuss the first dimension: Business Transformation.
The starting point for business transformation, of course, must be “no transformation.” As the organization gets a handle on their architecture and moves to first-generation SOA, IT moves into the role of service provider – not simply IT services, but also Web Services that automate the interaction with existing systems of record. Instead of simply integrating those systems, now the IT organization publishes interfaces that can be consumed as needed, transforming the relationship between IT and the business (which was always easier said than done, hence the relegation of first-generation SOA to Level One).
As the architecture matures to next-generation, Cloud-friendly SOA (which in many cases loses the “SOA” name, but is Service-oriented nevertheless), the transformation story centers on the move to the Cloud. Cloud Computing, you see, is far more than a change in technology deployment. It represents a force for transforming the business.
But even Cloud-driven transformation isn’t the end of the story. The move to Agile Architecture is a move to continuous business transformation – where the organization is as agile as it wants to be, and is able to deal with change as a routine part of how it does business. Continuous business transformation, of course, has always been the center of the Agile Architecture story – and is what we really mean when we say we want Digital Transformation.
The notion of customer journeys, of course, are central to the digital marketer’s playbook. Clearly, enterprises should focus their digital efforts on such journeys, as they represent customer interactions over time. But making customer journeys the centerpiece of the enterprise architecture, however, leaves more questions than answers. The challenge arises when EAs consider the context of the customer journey in the overall architecture as well as the architectural elements that make up each...
May. 2, 2016 03:15 AM EDT Reads: 1,975
In 2006, Martin Fowler posted his now famous essay on Continuous Integration. Looking back, what seemed revolutionary, radical or just plain crazy is now common, pedestrian and "just what you do." I love it. Back then, building and releasing software was a real pain. Integration was something you did at the end, after code complete, and we didn't know how long it would take. Some people may recall how we, as an industry, spent a massive amount of time integrating code from one team with another...
May. 2, 2016 12:30 AM EDT Reads: 890
As the software delivery industry continues to evolve and mature, the challenge of managing the growing list of the tools and processes becomes more daunting every day. Today, Application Lifecycle Management (ALM) platforms are proving most valuable by providing the governance, management and coordination for every stage of development, deployment and release. Recently, I spoke with Madison Moore at SD Times about the changing market and where ALM is headed.
May. 1, 2016 08:45 PM EDT Reads: 1,502
Struggling to keep up with increasing application demand? Learn how Platform as a Service (PaaS) can streamline application development processes and make resource management easy.
May. 1, 2016 08:15 PM EDT Reads: 2,093
If there is anything we have learned by now, is that every business paves their own unique path for releasing software- every pipeline, implementation and practices are a bit different, and DevOps comes in all shapes and sizes. Software delivery practices are often comprised of set of several complementing (or even competing) methodologies – such as leveraging Agile, DevOps and even a mix of ITIL, to create the combination that’s most suitable for your organization and that maximize your busines...
May. 1, 2016 08:00 PM EDT Reads: 1,845
The goal of any tech business worth its salt is to provide the best product or service to its clients in the most efficient and cost-effective way possible. This is just as true in the development of software products as it is in other product design services. Microservices, an app architecture style that leans mostly on independent, self-contained programs, are quickly becoming the new norm, so to speak. With this change comes a declining reliance on older SOAs like COBRA, a push toward more s...
May. 1, 2016 06:15 PM EDT Reads: 1,388
SYS-CON Events announced today that Peak 10, Inc., a national IT infrastructure and cloud services provider, will exhibit at SYS-CON's 18th International Cloud Expo®, which will take place on June 7-9, 2016, at the Javits Center in New York City, NY. Peak 10 provides reliable, tailored data center and network services, cloud and managed services. Its solutions are designed to scale and adapt to customers’ changing business needs, enabling them to lower costs, improve performance and focus inter...
May. 1, 2016 06:00 PM EDT Reads: 1,160
SYS-CON Events announced today that Stratoscale, the software company developing the next generation data center operating system, will exhibit at SYS-CON's 18th International Cloud Expo®, which will take place on June 7-9, 2016, at the Javits Center in New York City, NY. Stratoscale is revolutionizing the data center with a zero-to-cloud-in-minutes solution. With Stratoscale’s hardware-agnostic, Software Defined Data Center (SDDC) solution to store everything, run anything and scale everywhere...
May. 1, 2016 01:30 PM EDT Reads: 1,580
SYS-CON Events announced today that Men & Mice, the leading global provider of DNS, DHCP and IP address management overlay solutions, will exhibit at SYS-CON's 18th International Cloud Expo®, which will take place on June 7-9, 2016, at the Javits Center in New York City, NY. The Men & Mice Suite overlay solution is already known for its powerful application in heterogeneous operating environments, enabling enterprises to scale without fuss. Building on a solid range of diverse platform support,...
May. 1, 2016 12:15 PM EDT Reads: 2,332
You deployed your app with the Bluemix PaaS and it's gaining some serious traction, so it's time to make some tweaks. Did you design your application in a way that it can scale in the cloud? Were you even thinking about the cloud when you built the app? If not, chances are your app is going to break. Check out this webcast to learn various techniques for designing applications that will scale successfully in Bluemix, for the confidence you need to take your apps to the next level and beyond.
May. 1, 2016 11:45 AM EDT Reads: 1,499
Digital means customer preferences and behavior are driving enterprise technology decisions to be sure, but let’s not forget our employees. After all, when we say customer, we mean customer writ large, including partners, supply chain participants, and yes, those salaried denizens whose daily labor forms the cornerstone of the enterprise. While your customers bask in the warm rays of your digital efforts, are your employees toiling away in the dark recesses of your enterprise, pecking data into...
May. 1, 2016 08:15 AM EDT Reads: 1,062
Wow, if you ever wanted to learn about Rugged DevOps (some call it DevSecOps), sit down for a spell with Shannon Lietz, Ian Allison and Scott Kennedy from Intuit. We discussed a number of important topics including internal war games, culture hacking, gamification of Rugged DevOps and starting as a small team. There are 100 gold nuggets in this conversation for novices and experts alike.
May. 1, 2016 06:45 AM EDT Reads: 658
SYS-CON Events announced today that DatacenterDynamics has been named “Media Sponsor” of SYS-CON's 18th International Cloud Expo, which will take place on June 7–9, 2016, at the Javits Center in New York City, NY. DatacenterDynamics is a brand of DCD Group, a global B2B media and publishing company that develops products to help senior professionals in the world's most ICT dependent organizations make risk-based infrastructure and capacity decisions.
May. 1, 2016 06:30 AM EDT Reads: 2,506
With DevOps becoming more well-known and established practice in nearly every industry that delivers software, it is important to continually reassess its efficacy. This week’s top 10 includes a discussion on how the quick uptake of DevOps adoption in the enterprise has posed some serious challenges. Additionally, organizations who have taken the DevOps plunge must find ways to find, hire and keep their DevOps talent in order to keep the machine running smoothly.
May. 1, 2016 05:00 AM EDT Reads: 1,416
Between the mockups and specs produced by analysts, and resulting applications built by developers, there exists a gulf where projects fail, costs spiral, and applications disappoint. Methodologies like Agile attempt to address this with intensified communication, with partial success but many limitations. In his session at 18th Cloud Expo, Charles Kendrick, CTO & Chief Architect at Isomorphic Software, will present a revolutionary model enabled by new technologies. Learn how business and devel...
May. 1, 2016 04:15 AM EDT Reads: 1,749
Call it DevOps or not, if you are concerned about releasing more code faster and at a higher quality, the resulting software delivery chain and process will look and smell like DevOps. But for existing development teams, no matter what the velocity objective is, getting from here to there is not something that can be done without a plan. Moving your release cadence from months to weeks is not just about learning Agile practices and getting some automation tools. It involves people, tooling and ...
May. 1, 2016 04:15 AM EDT Reads: 1,515
Much of the discussion around cloud DevOps focuses on the speed with which companies need to get new code into production. This focus is important – because in an increasingly digital marketplace, new code enables new value propositions. New code is also often essential for maintaining competitive parity with market innovators. But new code doesn’t just have to deliver the functionality the business requires. It also has to behave well because the behavior of code in the cloud affects performan...
May. 1, 2016 02:45 AM EDT Reads: 1,407
This is not a small hotel event. It is also not a big vendor party where politicians and entertainers are more important than real content. This is Cloud Expo, the world's longest-running conference and exhibition focused on Cloud Computing and all that it entails. If you want serious presentations and valuable insight about Cloud Computing for three straight days, then register now for Cloud Expo.
Apr. 30, 2016 02:30 PM EDT Reads: 1,740
I had the opportunity to catch up with Chris Corriere - DevOps Engineer at AutoTrader - to talk about his experiences in the realm of Rugged DevOps. We discussed automation, culture and collaboration, and which thought leaders he is following. Chris Corriere: Hey, I'm Chris Corriere. I'm a DevOps Engineer AutoTrader. Derek Weeks: Today we're going to talk about Rugged DevOps. It's a subject that's gaining a lot of traction in the community but not a lot of people are really familiar with wh...
Apr. 30, 2016 09:45 AM EDT Reads: 1,588
APIs have taken the world by storm in recent years. The use of APIs has gone beyond just traditional "software" companies, to companies and organizations across industries using APIs to share information and power their applications. For some organizations, APIs are the biggest revenue drivers. For example, Salesforce generates nearly 50% of annual revenue through APIs. In other cases, APIs can increase a business's footprint and initiate collaboration. Netflix, for example, reported over 5 bi...
Apr. 29, 2016 09:30 PM EDT Reads: 2,579