|By Jason Bloomberg||
|July 28, 2014 07:21 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.
When we talk about the impact of BYOD and BYOA and the Internet of Things, we often focus on the impact on data center architectures. That's because there will be an increasing need for authentication, for access control, for security, for application delivery as the number of potential endpoints (clients, devices, things) increases. That means scale in the data center. What we gloss over, what we skip, is that before any of these "things" ever makes a request to access an application it had to...
Oct. 21, 2016 11:45 AM EDT Reads: 13,552
SYS-CON Events announced today that Transparent Cloud Computing (T-Cloud) Consortium will exhibit at the 19th International Cloud Expo®, which will take place on November 1–3, 2016, at the Santa Clara Convention Center in Santa Clara, CA. The Transparent Cloud Computing Consortium (T-Cloud Consortium) will conduct research activities into changes in the computing model as a result of collaboration between "device" and "cloud" and the creation of new value and markets through organic data proces...
Oct. 21, 2016 10:30 AM EDT Reads: 1,219
Without lifecycle traceability and visibility across the tool chain, stakeholders from Planning-to-Ops have limited insight and answers to who, what, when, why and how across the DevOps lifecycle. This impacts the ability to deliver high quality software at the needed velocity to drive positive business outcomes. In his general session at @DevOpsSummit at 19th Cloud Expo, Eric Robertson, General Manager at CollabNet, will discuss how customers are able to achieve a level of transparency that e...
Oct. 21, 2016 10:30 AM EDT Reads: 524
In many organizations governance is still practiced by phase or stage gate peer review, and Agile projects are forced to accommodate, which leads to WaterScrumFall or worse. But governance criteria and policies are often very weak anyway, out of date or non-existent. Consequently governance is frequently a matter of opinion and experience, highly dependent upon the experience of individual reviewers. As we all know, a basic principle of Agile methods is delegation of responsibility, and ideally ...
Oct. 21, 2016 10:00 AM EDT Reads: 2,957
Oct. 21, 2016 10:00 AM EDT Reads: 3,684
Today every business relies on software to drive the innovation necessary for a competitive edge in the Application Economy. This is why collaboration between development and operations, or DevOps, has become IT’s number one priority. Whether you are in Dev or Ops, understanding how to implement a DevOps strategy can deliver faster development cycles, improved software quality, reduced deployment times and overall better experiences for your customers.
Oct. 21, 2016 09:30 AM EDT Reads: 426
Apache Hadoop is a key technology for gaining business insights from your Big Data, but the penetration into enterprises is shockingly low. In fact, Apache Hadoop and Big Data proponents recognize that this technology has not yet achieved its game-changing business potential. In his session at 19th Cloud Expo, John Mertic, director of program management for ODPi at The Linux Foundation, will explain why this is, how we can work together as an open data community to increase adoption, and the i...
Oct. 21, 2016 08:15 AM EDT Reads: 1,835
All clouds are not equal. To succeed in a DevOps context, organizations should plan to develop/deploy apps across a choice of on-premise and public clouds simultaneously depending on the business needs. This is where the concept of the Lean Cloud comes in - resting on the idea that you often need to relocate your app modules over their life cycles for both innovation and operational efficiency in the cloud. In his session at @DevOpsSummit at19th Cloud Expo, Valentin (Val) Bercovici, CTO of So...
Oct. 21, 2016 07:45 AM EDT Reads: 2,055
JetBlue Airways uses virtual environments to reduce software development costs, centralize performance testing, and create a climate for continuous integration and real-time monitoring of mobile applications. The next BriefingsDirect Voice of the Customer performance engineering case study discussion examines how JetBlue Airways in New York uses virtual environments to reduce software development costs, centralize performance testing, and create a climate for continuous integration and real-tim...
Oct. 21, 2016 07:45 AM EDT Reads: 1,168
Virgil consists of an open-source encryption library, which implements Cryptographic Message Syntax (CMS) and Elliptic Curve Integrated Encryption Scheme (ECIES) (including RSA schema), a Key Management API, and a cloud-based Key Management Service (Virgil Keys). The Virgil Keys Service consists of a public key service and a private key escrow service.
Oct. 21, 2016 07:15 AM EDT Reads: 877
SYS-CON Events announced today that eCube Systems, the leading provider of modern development tools and best practices for Continuous Integration on OpenVMS, will exhibit at SYS-CON's @DevOpsSummit at Cloud Expo New York, which will take place on June 7-9, 2016, at the Javits Center in New York City, NY. eCube Systems offers a family of middleware products and development tools that maximize return on technology investment by leveraging existing technical equity to meet evolving business needs. ...
Oct. 21, 2016 07:00 AM EDT Reads: 4,391
Let's just nip the conflation of these terms in the bud, shall we?
"MIcro" is big these days. Both microservices and microsegmentation are having and will continue to have an impact on data center architecture, but not necessarily for the same reasons. There's a growing trend in which folks - particularly those with a network background - conflate the two and use them to mean the same thing.
They are not.
One is about the application. The other, the network. T...
Oct. 21, 2016 06:45 AM EDT Reads: 6,306
This is a no-hype, pragmatic post about why I think you should consider architecting your next project the way SOA and/or microservices suggest. No matter if it’s a greenfield approach or if you’re in dire need of refactoring. Please note: considering still keeps open the option of not taking that approach. After reading this, you will have a better idea about whether building multiple small components instead of a single, large component makes sense for your project. This post assumes that you...
Oct. 21, 2016 06:00 AM EDT Reads: 7,150
DevOps is speeding towards the IT world like a freight train and the hype around it is deafening. There is no reason to be afraid of this change as it is the natural reaction to the agile movement that revolutionized development just a few years ago. By definition, DevOps is the natural alignment of IT performance to business profitability. The relevance of this has yet to be quantified but it has been suggested that the route to the CEO’s chair will come from the IT leaders that successfully ma...
Oct. 21, 2016 04:30 AM EDT Reads: 16,208
@DevOpsSummit has been named the ‘Top DevOps Influencer' by iTrend. iTrend processes millions of conversations, tweets, interactions, news articles, press releases, blog posts - and extract meaning form them and analyzes mobile and desktop software platforms used to communicate, various metadata (such as geo location), and automation tools. In overall placement, @DevOpsSummit ranked as the number one ‘DevOps Influencer' followed by @CloudExpo at third, and @MicroservicesE at 24th.
Oct. 21, 2016 03:30 AM EDT Reads: 3,771
Without lifecycle traceability and visibility across the tool chain, stakeholders from Planning-to-Ops have limited insight and answers to who, what, when, why and how across the DevOps lifecycle. This impacts the ability to deliver high quality software at the needed velocity to drive positive business outcomes. In his session at @DevOpsSummit 19th Cloud Expo, Eric Robertson, General Manager at CollabNet, will show how customers are able to achieve a level of transparency that enables everyon...
Oct. 21, 2016 02:30 AM EDT Reads: 1,216
Explosive growth in connected devices. Enormous amounts of data for collection and analysis. Critical use of data for split-second decision making and actionable information. All three are factors in making the Internet of Things a reality. Yet, any one factor would have an IT organization pondering its infrastructure strategy. How should your organization enhance its IT framework to enable an Internet of Things implementation? In his session at @ThingsExpo, James Kirkland, Red Hat's Chief Arch...
Oct. 21, 2016 02:00 AM EDT Reads: 5,912
As software becomes more and more complex, we, as software developers, have been splitting up our code into smaller and smaller components. This is also true for the environment in which we run our code: going from bare metal, to VMs to the modern-day Cloud Native world of containers, schedulers and microservices. While we have figured out how to run containerized applications in the cloud using schedulers, we've yet to come up with a good solution to bridge the gap between getting your conta...
Oct. 21, 2016 01:30 AM EDT Reads: 1,356
DevOps theory promotes a culture of continuous improvement built on collaboration, empowerment, systems thinking, and feedback loops. But how do you collaborate effectively across the traditional silos? How can you make decisions without system-wide visibility? How can you see the whole system when it is spread across teams and locations? How do you close feedback loops across teams and activities delivering complex multi-tier, cloud, container, serverless, and/or API-based services?
Oct. 21, 2016 12:30 AM EDT Reads: 916
SYS-CON Events announced today that Super Micro Computer, Inc., a global leader in Embedded and IoT solutions, will exhibit at SYS-CON's 20th International Cloud Expo®, which will take place on June 7-9, 2017, at the Javits Center in New York City, NY. Supermicro (NASDAQ: SMCI), the leading innovator in high-performance, high-efficiency server technology, is a premier provider of advanced server Building Block Solutions® for Data Center, Cloud Computing, Enterprise IT, Hadoop/Big Data, HPC and ...
Oct. 21, 2016 12:15 AM EDT Reads: 3,465