Welcome!

Microservices Expo Authors: Stackify Blog, Aruna Ravichandran, Dalibor Siroky, Kevin Jackson, PagerDuty Blog

Related Topics: @DevOpsSummit, Microservices Expo, @CloudExpo, @ThingsExpo

@DevOpsSummit: Article

Threads of Digital Architecture | @CloudExpo #IoT #M2M #DigitalTransformation

Customers are simply too fickle in their desires to expect traditional architecture to rise to the challenge

In last week's Cortex newsletter, I introduced the following diagram of a customer-centric digital architecture, where digital architecture is shorthand for enterprise architecture that's laser focused on driving digital transformation.

 

Customer-Centric Digital Architecture

In the diagram above, the traditional architectural layers (represented here as concentric bands) have been grayed out in favor of customer journeys that cut across user interface, process, technology infrastructure, and data concerns, instead focusing on the preferences and behavior of individual customers as they conduct all their interactions with the company in question.

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 customer journey. After all, dividing up the world into familiar layers like process, data, and technology is relatively straightforward. There are overlaps and ambiguities at the edges to be sure, but everyone approaches such layers with a relatively common understanding of the overall scope of each layer and what belongs within each one.

Approaching the enterprise architecture as a customer-centric digital architecture, however, requires more than drawing new boxes and sorting things into them. Rather, such architecture must take a different approach than EA has been done before, or the end result won't meet the business need - which in this case, centers on addressing always-changing customer preferences and behavior. Customers are simply too fickle in their desires to expect traditional architecture to rise to the challenge.

The Three Threads of Digital Architecture
In order to flesh out this new approach, we need to pull together three threads in the tangled weave we call digital transformation: traditional EA, Agile, and scaled self-organization.

From traditional EA we take a reductionist approach to solving problems: breaking them up into well-defined chunks that have well-defined relationships with each other. This ‘boxes and lines' notion of architecture is familiar to every architect, of course, and hearkens back to the Zachman Framework, TOGAF, and just about any other EA framework you care to mention.

Reductionist approaches, however, only take us so far, because they assume a level of understanding and stability that the real world rarely if ever offers.

If only we had a clear, stable understanding of our requirements that everybody agreed on, and only if our ‘final state' was similarly clearly defined, then our architecture would be straightforward.

We all realize by now, however, that such ‘waterfall' thinking almost always leads us astray, because rarely if ever do the assumptions listed above hold true. Instead, we should always assume that we don't understand the requirements, that there's no such thing as a ‘final state,' and furthermore, we must also take for granted that everything is always in a state of flux.

Fortunately, we have an established set of principles for dealing with situations of unclear, continually shifting requirements - the principles we loosely group under the Agile banner: iterative, customer-focused approaches that focus on solving the problem at hand instead of other, less important tasks.

So far so good, but while combining Agile principles with EA - what people predictably call ‘Agile EA' - is an important step in the right direction, it doesn't take us far enough to solve the challenges we have with Digital Architecture.

The problem: Agile principles focus primarily at the local, team level. And while there are several approaches to scaling Agile, like the Scaled Agile Framework (SAFe), for example, they all suffer the same fate: as they rise from the team level to the enterprise level, they lose the inherent agility that is necessary to satisfy the preferences and behavior of customers that form the basis of digital architecture.

Solving this problem requires us to pull on the third thread of digital architecture: self-organization. Not merely the team-level self-organization that has been a part of Agile since day one, but rather self-organization scaled across the enterprise.

The Missing Piece of the Digital Architecture Puzzle
Circling back to our original questions about customer journeys at the architectural level - the context of each journey in the architecture as well as the relationships among journeys - the answer lies in scaled self-organization, within the context of Agile EA.

Let's take an example. Say you're an executive at a large consumer bank, and you realize your interactions with customers are sorely lacking. It would be easy to say you need a better mobile banking app - and perhaps you do - but focusing on a single app rather than the entire customer journey won't solve the larger problem.

In reality, the customer journey involves not just the mobile app and your web site, but also your call center, your outbound marketing, your branches, and of course, all the back end systems that make everything work. And then you also realize that even this list is likely to be dangerously incomplete.

So, who do you turn to in order to put together all the people and other resources across numerous departments to get the customer journey right? And how do you place this particular customer journey initiative into the context of all the other digital initiatives that are clamoring for attention and resources?

The answer is to call upon the people who know best what your bank does, and furthermore, what it can do - your own employees. Follow the basics of self-organization (see my previous Cortex newsletters, Conway's Law and the Emergence of Business Agility and Fixing Slow the Agile Digital Transformation Way for more details), and then get out of their way. (Subscribe to the Cortex newsletter here.)

The Intellyx Take
What, then, is the role of the EAs in this vision of scalable self-organization? First and foremost, they are on the self-organizing teams themselves, including both the teams that form around specific business challenges as well as the Center for Digital Empowerment that helps to coordinate and empower all the digital efforts across the enterprise.

As for the enterprise architecture itself, its focus is on facilitating the transition to scalable self-organization, within the context of Agile EA. There may still be boxes and lines, perhaps, but the EAs must move each element, each box and line, up a level of abstraction.

Instead of a box representing a piece of technology, the box represents a self-organizing team's dynamic choice of technology. Instead of a box representing a process, that box represents once again the result of a self-organizing team's choice about a process.

The overall digital architecture, therefore, represents self-organizing teams' approach to answering the basic questions about the context and content of customer journeys, rather than the context and content of those journeys themselves.

Only by working at this ‘meta' level will the architecture ever account for the inherent agility necessary to address ever-changing customer preferences and behavior in the context of a digitally transforming organization.

The goal of EA, of course, is building business agility as a core competency across the enterprise. It's not good enough to change, your organization must get better at change. After all, you cannot eliminate change. You cannot even simplify it. Digital architecture must embrace change.

Intellyx advises companies on their digital transformation initiatives and helps vendors communicate their agility stories. As of the time of writing, none of the organizations mentioned in this article are Intellyx customers. Image credits: Willi Heidelbach and Intellyx.

More Stories By Jason Bloomberg

Jason Bloomberg is the leading expert on architecting agility for the enterprise. As president of Intellyx, Mr. Bloomberg brings his years of thought leadership in the areas of Cloud Computing, Enterprise Architecture, and Service-Oriented Architecture to a global clientele of business executives, architects, software vendors, and Cloud service providers looking to achieve technology-enabled business agility across their organizations and for their customers. His latest book, The Agile Architecture Revolution (John Wiley & Sons, 2013), sets the stage for Mr. Bloomberg’s groundbreaking Agile Architecture vision.

Mr. Bloomberg is perhaps best known for his twelve years at ZapThink, where he created and delivered the Licensed ZapThink Architect (LZA) SOA course and associated credential, certifying over 1,700 professionals worldwide. He is one of the original Managing Partners of ZapThink LLC, the leading SOA advisory and analysis firm, which was acquired by Dovel Technologies in 2011. He now runs the successor to the LZA program, the Bloomberg Agile Architecture Course, around the world.

Mr. Bloomberg is a frequent conference speaker and prolific writer. He has published over 500 articles, spoken at over 300 conferences, Webinars, and other events, and has been quoted in the press over 1,400 times as the leading expert on agile approaches to architecture in the enterprise.

Mr. Bloomberg’s previous book, Service Orient or Be Doomed! How Service Orientation Will Change Your Business (John Wiley & Sons, 2006, coauthored with Ron Schmelzer), is recognized as the leading business book on Service Orientation. He also co-authored the books XML and Web Services Unleashed (SAMS Publishing, 2002), and Web Page Scripting Techniques (Hayden Books, 1996).

Prior to ZapThink, Mr. Bloomberg built a diverse background in eBusiness technology management and industry analysis, including serving as a senior analyst in IDC’s eBusiness Advisory group, as well as holding eBusiness management positions at USWeb/CKS (later marchFIRST) and WaveBend Solutions (now Hitachi Consulting).

@MicroservicesExpo Stories
How is DevOps going within your organization? If you need some help measuring just how well it is going, we have prepared a list of some key DevOps metrics to track. These metrics can help you understand how your team is doing over time. The word DevOps means different things to different people. Some say it a culture and every vendor in the industry claims that their tools help with DevOps. Depending on how you define DevOps, some of these metrics may matter more or less to you and your team.
For many of us laboring in the fields of digital transformation, 2017 was a year of high-intensity work and high-reward achievement. So we’re looking forward to a little breather over the end-of-year holiday season. But we’re going to have to get right back on the Continuous Delivery bullet train in 2018. Markets move too fast and customer expectations elevate too precipitously for businesses to rest on their laurels. Here’s a DevOps “to-do list” for 2018 that should be priorities for anyone w...
If testing environments are constantly unavailable and affected by outages, release timelines will be affected. You can use three metrics to measure stability events for specific environments and plan around events that will affect your critical path to release.
In a recent post, titled “10 Surprising Facts About Cloud Computing and What It Really Is”, Zac Johnson highlighted some interesting facts about cloud computing in the SMB marketplace: Cloud Computing is up to 40 times more cost-effective for an SMB, compared to running its own IT system. 94% of SMBs have experienced security benefits in the cloud that they didn’t have with their on-premises service
DevOps failure is a touchy subject with some, because DevOps is typically perceived as a way to avoid failure. As a result, when you fail in a DevOps practice, the situation can seem almost hopeless. However, just as a fail-fast business approach, or the “fail and adjust sooner” methodology of Agile often proves, DevOps failures are actually a step in the right direction. They’re the first step toward learning from failures and turning your DevOps practice into one that will lead you toward even...
DevOps is under attack because developers don’t want to mess with infrastructure. They will happily own their code into production, but want to use platforms instead of raw automation. That’s changing the landscape that we understand as DevOps with both architecture concepts (CloudNative) and process redefinition (SRE). Rob Hirschfeld’s recent work in Kubernetes operations has led to the conclusion that containers and related platforms have changed the way we should be thinking about DevOps and...
While walking around the office I happened upon a relatively new employee dragging emails from his inbox into folders. I asked why and was told, “I’m just answering emails and getting stuff off my desk.” An empty inbox may be emotionally satisfying to look at, but in practice, you should never do it. Here’s why. I recently wrote a piece arguing that from a mathematical perspective, Messy Desks Are Perfectly Optimized. While it validated the genius of my friends with messy desks, it also gener...
The goal of Microservices is to improve software delivery speed and increase system safety as scale increases. Microservices being modular these are faster to change and enables an evolutionary architecture where systems can change, as the business needs change. Microservices can scale elastically and by being service oriented can enable APIs natively. Microservices also reduce implementation and release cycle time and enables continuous delivery. This paper provides a logical overview of the Mi...
The next XaaS is CICDaaS. Why? Because CICD saves developers a huge amount of time. CD is an especially great option for projects that require multiple and frequent contributions to be integrated. But… securing CICD best practices is an emerging, essential, yet little understood practice for DevOps teams and their Cloud Service Providers. The only way to get CICD to work in a highly secure environment takes collaboration, patience and persistence. Building CICD in the cloud requires rigorous ar...
The enterprise data storage marketplace is poised to become a battlefield. No longer the quiet backwater of cloud computing services, the focus of this global transition is now going from compute to storage. An overview of recent storage market history is needed to understand why this transition is important. Before 2007 and the birth of the cloud computing market we are witnessing today, the on-premise model hosted in large local data centers dominated enterprise storage. Key marketplace play...
The cloud revolution in enterprises has very clearly crossed the phase of proof-of-concepts into a truly mainstream adoption. One of most popular enterprise-wide initiatives currently going on are “cloud migration” programs of some kind or another. Finding business value for these programs is not hard to fathom – they include hyperelasticity in infrastructure consumption, subscription based models, and agility derived from rapid speed of deployment of applications. These factors will continue to...
Some people are directors, managers, and administrators. Others are disrupters. Eddie Webb (@edwardawebb) is an IT Disrupter for Software Development Platforms at Liberty Mutual and was a presenter at the 2016 All Day DevOps conference. His talk, Organically DevOps: Building Quality and Security into the Software Supply Chain at Liberty Mutual, looked at Liberty Mutual's transformation to Continuous Integration, Continuous Delivery, and DevOps. For a large, heavily regulated industry, this task ...
Following a tradition dating back to 2002 at ZapThink and continuing at Intellyx since 2014, it’s time for Intellyx’s annual predictions for the coming year. If you’re a long-time fan, you know we have a twist to the typical annual prediction post: we actually critique our predictions from the previous year. To make things even more interesting, Charlie and I switch off, judging the other’s predictions. And now that he’s been with Intellyx for more than a year, this Cortex represents my first ...
"Grape Up leverages Cloud Native technologies and helps companies build software using microservices, and work the DevOps agile way. We've been doing digital innovation for the last 12 years," explained Daniel Heckman, of Grape Up in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
The Toyota Production System, a world-renowned production system is based on the "complete elimination of all waste". The "Toyota Way", grounded on continuous improvement dates to the 1860s. The methodology is widely proven to be successful yet there are still industries within and tangential to manufacturing struggling to adopt its core principles: Jidoka: a process should stop when an issue is identified prevents releasing defective products
We seem to run this cycle with every new technology that comes along. A good idea with practical applications is born, then both marketers and over-excited users start to declare it is the solution for all or our problems. Compliments of Gartner, we know it generally as “The Hype Cycle”, but each iteration is a little different. 2018’s flavor will be serverless computing, and by 2018, I mean starting now, but going most of next year, you’ll be sick of it. We are already seeing people write such...
Defining the term ‘monitoring’ is a difficult task considering the performance space has evolved significantly over the years. Lately, there has been a shift in the monitoring world, sparking a healthy debate regarding the definition and purpose of monitoring, through which a new term has emerged: observability. Some of that debate can be found in blogs by Charity Majors and Cindy Sridharan.
It’s “time to move on from DevOps and continuous delivery.” This was the provocative title of a recent article in ZDNet, in which Kelsey Hightower, staff developer advocate at Google Cloud Platform, suggested that “software shops should have put these concepts into action years ago.” Reading articles like this or listening to talks at most DevOps conferences might make you think that we’re entering a post-DevOps world. But vast numbers of organizations still struggle to start and drive transfo...
Let's do a visualization exercise. Imagine it's December 31, 2018, and you're ringing in the New Year with your friends and family. You think back on everything that you accomplished in the last year: your company's revenue is through the roof thanks to the success of your product, and you were promoted to Lead Developer. 2019 is poised to be an even bigger year for your company because you have the tools and insight to scale as quickly as demand requires. You're a happy human, and it's not just...
"Opsani helps the enterprise adopt containers, help them move their infrastructure into this modern world of DevOps, accelerate the delivery of new features into production, and really get them going on the container path," explained Ross Schibler, CEO of Opsani, and Peter Nickolov, CTO of Opsani, in this SYS-CON.tv interview at DevOps Summit at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.