Welcome!

Microservices Expo Authors: Dalibor Siroky, Elizabeth White, Pat Romanski, John Katrick, Liz McMillan

Related Topics: @DevOpsSummit, Microservices Expo, Linux Containers, Open Source Cloud, Containers Expo Blog, Machine Learning

@DevOpsSummit: Article

Fixing the Agile Digital Transformation | @DevOpsSummit #Agile #DevOps

Virtually every large organization has a massive boat anchor dragging them down – slow IT.

Enterprises are finally realizing that digital transformation must be end-to-end if they want to remain competitive in today’s software-driven, customer-focused world – but virtually every large organization has a massive boat anchor dragging them down – slow IT.

Legacy technology woes are bad enough – but what really makes slow IT slow are the people and the processes they follow. Nobody likes to change, yet change is what digital transformation is all about.

Some organizations look for shortcuts. Let fast go fast and let slow go slow, Gartner says – but that road leads to ruin, as competitiveness slips through the fingers of executives fool enough to take such advice.

Instead, we must fix slow. Not an easy task, to be sure – but nevertheless quite achievable. And yet, every enterprise will face its unique challenges as it wends its way toward successful transformation. In spite of all the roadblocks, however, there is a straightforward path to achieving the change necessary – the agile digital transformation way.

Getting to Square Zero
The real work of digital transformation can’t even begin until an organization has cleaned up the worst of its particularly nasty messes. For example, if your IT shop doesn’t know what applications it is responsible for or has no idea what systems talk to which, then you have issues you must address before you can begin.

Similarly, in many cases the challenges are organizational or process-centric – and while there are always certain similarities from one organization to another, every situation is different, and thus calls for a different approach.

In keeping with the ‘agile’ part of agile digital transformation, therefore, the best course of action is to fix what’s broken iteratively, with a constant focus on customer priorities to drive the decision making process as to what you should fix first.

Make no mistake – you’re eating an elephant here, so your best bet is ‘one bite at a time.’ Instead of facing an intractable morass all at once, break up the challenge into tasks that your organization can accomplish, and repeat as necessary. It’s far more desirable to be successful at a series of smaller tasks than to fail spectacularly upon attempting to tackle a transformation initiative as a big-bang effort.

Be careful, however, to avoid being dogmatic in your approach. Don’t follow any particular methodology if it doesn’t meet the needs of the day. Better to be iconoclastic and throw away rules and advice that don’t suit the situation at hand. If any consultant or analyst firm or management guru gives you a recipe to follow, don’t take their advice simply because they give it.

Beware the Three Fallacies of IT Decision Making
Three common fallacies – untruths that nevertheless seem true – derail many a transformation initiative. The best way to avoid such a fate is to understand and recognize the erroneous thought patterns when they occur.

I discussed the first fallacy in my last Cortex newsletter: failing to consider opportunity risk when evaluating your risk profile. Lowering risk short term only to drive your enterprise into an uncompetitive death spiral is a fallacious risk calculation. Don’t do it!

The second fallacy to avoid is the sunk cost (AKA good money after bad) fallacy. The fact you’ve already spent money on an approach is not a good reason to stick with it if a better approach presents itself. If you spent $10 million on that dinosaur of an ERP system, for example, and today you realize there’s a far more flexible, cloud-based alternative that will cost you less starting today, those $10 million shouldn’t figure into your decision making.

The third fallacy actually has two sides to it. The first side: the ‘shiny things’ fallacy. Don’t base a decision on the fact that some new technology or approach is the new, cool, ‘in’ thing to do. Every year there are new buzzwords – Containers! Microservices! Cognitive computing! Such technologies may or may not meet your needs, but don’t let the fact that they are hot buzzwords sway your decision.

The converse of the shiny things fallacy is the ‘legacy’ fallacy – assuming that just because something is old or out of fashion, then it’s necessarily a good idea to get rid of it. Mainframes in particular are especially susceptible to this fallacy, as younger CIOs jump to the conclusion that digital transformation requires the retirement of these workhorses of IT. As I’ve written before, however, such reasoning is fallacious. The bottom line: if it ain’t broke, don’t fix it.

The Key to Organizational Change
I’ve written in earlier articles
about how self-organization is essential for building agile organizations, and is thus critically important to any digital transformation initiative. How, then, do you introduce self-organizational principles to the hidebound, rigidly hierarchical organizational structures and associated business processes of slow IT?

The answer: DevOps. If you’re not ‘doing’ DevOps (for want of a better verb), then start. If you are doing DevOps (but poorly), then get better at it. DevOps perking along nicely? Then extend it horizontally, beyond just dev and ops to SecDevOps and BizDevOps. The names don’t matter, but the approach does.

DevOps is more than just a way to build better software faster. It’s even more than a cultural shift that drives such improvements. DevOps is a self-organization ‘virus’ that can infect your whole enterprise with self-organizing principles that drive agility at velocity.

DevOps – or DevOps-like principles, as we don’t want to be overly dogmatic here – are the key to changing the culture, not just in IT, but across the organization. Even if your company doesn’t develop software internally, you should still move to a DevOps organizational model. It will be different from the DevOps we see in software development shops to be sure, but you should still do it.

Make the Most of Self-Organizing Change
As a DevOps-like self-organizing model takes hold in your organization, it will supplant and eventually replace traditional hierarchical thinking. There’s a good chance that many people won’t want to come along on this ride, and that’s fine. So pay people to leave if they’re not with the program.

Those people who stay – especially management – will require retraining and reassignment, or more precisely, the absence of assignment. There’s no need for layers of management in a digitally transformed enterprise. Leaders will naturally arise from the self-organization process, and those people are the leaders you actually need.

Companies like Zappos and WL Gore have implemented such management approaches, but that doesn’t mean you should follow their examples (or anyone else’s) too closely. Remember, be iconoclastic. Let your own people resolve the details of the organizational models that will work for your organization.

Self-organizing teams will figure out how to negotiate the efficiency vs. flexibility tradeoff. Sometimes efficiency wins out, but imposing an organizational structure that favors efficiency over flexibility may lead to optimal business outcomes in the short term, but will stifle innovation in the process.

Target Slow Governance
The mishmash of organizational constructs and delay-ridden processes we call governance are perhaps the primary culprit that make slow IT so slow. The solution is a combination of self-organization and automation that not coincidentally follows DevOps patterns.

SecDevOps, for example, shifts security considerations ‘to the left’ (that is, toward the beginning of relevant iterations), and furthermore, seeks to automate policy enforcement following continuous integration/continuous delivery models.

Where security goes, all governance should follow. From the strictures of the architecture review board to the audits from the compliance division, the focus should be on self-organization and automation. Don’t be a gatekeeper. Instead, become an enabler.

Enterprise architects, of course, play an important role in this transformation. We don’t need more gatekeepers among this crowd either. Instead, EAs should help to self-organize Centers for Digital Enablement – teams that facilitate digital best practices across the organization, in particular, a culture of self-service.

The Intellyx Take: The ‘Agile’ in Agile Digital Transformation
There’s far more to fixing slow than one 1,400-word article can cover, of course. Furthermore, the devil will always be in the details. And of course, if I could give you a recipe for success, then my advice would be to not follow the recipe!

In the absence of such a recipe, therefore, seek the big picture – and in this case, the big picture is the nature of organizational transformation. We’re not simply taking the old way of doing things and switching it out for the new way. This is no simple change management puzzle. Instead, we’re seeking to reinvent how we think about doing things altogether.

We have a true paradigm shift on our hands here, as we’re discarding deeply held notions that the business world has clung to for centuries. In their place: a new way of building and running large organizations to be more agile, and thus rise to the challenges of meeting ever-changing customer demands. Welcome to the world of agile digital transformation.

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 credit: USFWS.

 

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.