|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.
It’s been proven time and time again that in tech, diversity drives greater innovation, better team productivity and greater profits and market share. So what can we do in our DevOps teams to embrace diversity and help transform the culture of development and operations into a true “DevOps” team? In her session at DevOps Summit, Stefana Muller, Director, Product Management – Continuous Delivery at CA Technologies, answered that question citing examples, showing how to create opportunities for ...
Aug. 30, 2015 01:00 AM EDT Reads: 470
Whether you like it or not, DevOps is on track for a remarkable alliance with security. The SEC didn’t approve the merger. And your boss hasn’t heard anything about it. Yet, this unruly triumvirate will soon dominate and deliver DevSecOps faster, cheaper, better, and on an unprecedented scale. In his session at DevOps Summit, Frank Bunger, VP of Customer Success at ScriptRock, will discuss how this cathartic moment will propel the DevOps movement from such stuff as dreams are made on to a prac...
Aug. 30, 2015 01:00 AM EDT Reads: 203
SYS-CON Events announced today that DataClear Inc. will exhibit at the 17th International Cloud Expo®, which will take place on November 3–5, 2015, at the Santa Clara Convention Center in Santa Clara, CA. The DataClear ‘BlackBox’ is the only solution that moves your PC, browsing and data out of the United States and away from prying (and spying) eyes. Its solution automatically builds you a clean, on-demand, virus free, new virtual cloud based PC outside of the United States, and wipes it clean...
Aug. 29, 2015 07:15 PM EDT Reads: 369
In his session at 17th Cloud Expo, Ernest Mueller, Product Manager at Idera, will explain the best practices and lessons learned for tracking and optimizing costs while delivering a cloud-hosted service. He will describe a DevOps approach where the applications and systems work together to track usage, model costs in a granular fashion, and make smart decisions at runtime to minimize costs. The trickier parts covered include triggering off the right metrics; balancing resilience and redundancy ...
Aug. 29, 2015 05:00 PM EDT Reads: 166
Culture is the most important ingredient of DevOps. The challenge for most organizations is defining and communicating a vision of beneficial DevOps culture for their organizations, and then facilitating the changes needed to achieve that. Often this comes down to an ability to provide true leadership. As a CIO, are your direct reports IT managers or are they IT leaders? The hard truth is that many IT managers have risen through the ranks based on their technical skills, not their leadership ab...
Aug. 29, 2015 04:00 PM EDT Reads: 322
Several years ago, I was a developer in a travel reservation aggregator. Our mission was to pull flight and hotel data from a bunch of cryptic reservation platforms, and provide it to other companies via an API library - for a fee. That was before companies like Expedia standardized such things. We started with simple methods like getFlightLeg() or addPassengerName(), each performing a small, well-understood function. But our customers wanted bigger, more encompassing services that would "do ...
Aug. 29, 2015 03:00 PM EDT Reads: 215
SYS-CON Events announced today that Pythian, a global IT services company specializing in helping companies leverage disruptive technologies to optimize revenue-generating systems, has been named “Bronze Sponsor” of SYS-CON's 17th Cloud Expo, which will take place on November 3–5, 2015, at the Santa Clara Convention Center in Santa Clara, CA. Founded in 1997, Pythian is a global IT services company that helps companies compete by adopting disruptive technologies such as cloud, Big Data, advance...
Aug. 29, 2015 11:00 AM EDT Reads: 249
Early in my DevOps Journey, I was introduced to a book of great significance circulating within the Web Operations industry titled The Phoenix Project. (You can read our review of Gene’s book, if interested.) Written as a novel and loosely based on many of the same principles explored in The Goal, this book has been read and referenced by many who have adopted DevOps into their continuous improvement and software delivery processes around the world. As I began planning my travel schedule last...
Aug. 29, 2015 10:00 AM EDT Reads: 507
Docker containerization is increasingly being used in production environments. How can these environments best be monitored? Monitoring Docker containers as if they are lightweight virtual machines (i.e., monitoring the host from within the container), with all the common metrics that can be captured from an operating system, is an insufficient approach. Docker containers can’t be treated as lightweight virtual machines; they must be treated as what they are: isolated processes running on hosts....
Aug. 29, 2015 10:00 AM EDT Reads: 125
What does “big enough” mean? It’s sometimes useful to argue by reductio ad absurdum. Hello, world doesn’t need to be broken down into smaller services. At the other extreme, building a monolithic enterprise resource planning (ERP) system is just asking for trouble: it’s too big, and it needs to be decomposed.
Aug. 29, 2015 10:00 AM EDT Reads: 334
SYS-CON Events announced today that G2G3 will exhibit at SYS-CON's @DevOpsSummit Silicon Valley, which will take place on November 3–5, 2015, at the Santa Clara Convention Center in Santa Clara, CA. Based on a collective appreciation for user experience, design, and technology, G2G3 is uniquely qualified and motivated to redefine how organizations and people engage in an increasingly digital world.
Aug. 29, 2015 09:30 AM EDT Reads: 435
SYS-CON Events announced today that HPM Networks will exhibit at the 17th International Cloud Expo®, which will take place on November 3–5, 2015, at the Santa Clara Convention Center in Santa Clara, CA. For 20 years, HPM Networks has been integrating technology solutions that solve complex business challenges. HPM Networks has designed solutions for both SMB and enterprise customers throughout the San Francisco Bay Area.
Aug. 29, 2015 09:30 AM EDT Reads: 854
Introducing Containers & Microservices Bootcamp at @CloudExpo Silicon Valley | #Containers #Microservices
SYS-CON Events announced today the Containers & Microservices Bootcamp, being held November 3-4, 2015, in conjunction with 17th Cloud Expo, @ThingsExpo, and @DevOpsSummit at the Santa Clara Convention Center in Santa Clara, CA. This is your chance to get started with the latest technology in the industry. Combined with real-world scenarios and use cases, the Containers and Microservices Bootcamp, led by Janakiram MSV, a Microsoft Regional Director, will include presentations as well as hands-on...
Aug. 29, 2015 09:15 AM EDT Reads: 241
The pricing of tools or licenses for log aggregation can have a significant effect on organizational culture and the collaboration between Dev and Ops teams. Modern tools for log aggregation (of which Logentries is one example) can be hugely enabling for DevOps approaches to building and operating business-critical software systems. However, the pricing of an aggregated logging solution can affect the adoption of modern logging techniques, as well as organizational capabilities and cross-team ...
Aug. 29, 2015 08:30 AM EDT Reads: 366
In today's digital world, change is the one constant. Disruptive innovations like cloud, mobility, social media, and the Internet of Things have reshaped the market and set new standards in customer expectations. To remain competitive, businesses must tap the potential of emerging technologies and markets through the rapid release of new products and services. However, the rigid and siloed structures of traditional IT platforms and processes are slowing them down – resulting in lengthy delivery ...
Aug. 29, 2015 07:45 AM EDT Reads: 557
Skeuomorphism usually means retaining existing design cues in something new that doesn’t actually need them. However, the concept of skeuomorphism can be thought of as relating more broadly to applying existing patterns to new technologies that, in fact, cry out for new approaches. In his session at DevOps Summit, Gordon Haff, Senior Cloud Strategy Marketing and Evangelism Manager at Red Hat, discussed why containers should be paired with new architectural practices such as microservices rathe...
Aug. 29, 2015 06:00 AM EDT Reads: 380
Any Ops team trying to support a company in today’s cloud-connected world knows that a new way of thinking is required – one just as dramatic than the shift from Ops to DevOps. The diversity of modern operations requires teams to focus their impact on breadth vs. depth. In his session at DevOps Summit, Adam Serediuk, Director of Operations at xMatters, Inc., will discuss the strategic requirements of evolving from Ops to DevOps, and why modern Operations has begun leveraging the “NoOps” approa...
Aug. 29, 2015 05:30 AM EDT Reads: 351
Puppet Labs has announced the next major update to its flagship product: Puppet Enterprise 2015.2. This release includes new features providing DevOps teams with clarity, simplicity and additional management capabilities, including an all-new user interface, an interactive graph for visualizing infrastructure code, a new unified agent and broader infrastructure support.
Aug. 29, 2015 03:00 AM EDT Reads: 482
DevOps has traditionally played important roles in development and IT operations, but the practice is quickly becoming core to other business functions such as customer success, business intelligence, and marketing analytics. Modern marketers today are driven by data and rely on many different analytics tools. They need DevOps engineers in general and server log data specifically to do their jobs well. Here’s why: Server log files contain the only data that is completely full and accurate in th...
Aug. 29, 2015 12:15 AM EDT Reads: 344
The Microservices architectural pattern promises increased DevOps agility and can help enable continuous delivery of software. This session is for developers who are transforming existing applications to cloud-native applications, or creating new microservices style applications. In his session at DevOps Summit, Jim Bugwadia, CEO of Nirmata, will introduce best practices, patterns, challenges, and solutions for the development and operations of microservices style applications. He will discuss ...
Aug. 27, 2015 02:15 PM EDT Reads: 507