Welcome!

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

Related Topics: @DevOpsSummit, Microservices Expo, @CloudExpo

@DevOpsSummit: Blog Feed Post

The Emergence of Business Agility By @TheEbizWizard | @DevOpsSummit #DevOps

The law is more of an observation of correlations between system designs and communication structures

Conway's Law and the Emergence of Business Agility

In my last Cortex newsletter, I discussed the history of Conway’s Law, and took a close look at how this erstwhile law can help us understand the reorganizations and deeper cultural shifts behind devops and digital transformation.

The law – “any organization that designs a system will inevitably produce a design whose structure is a copy of the organization’s communication structure” – is more of an observation of correlations between system designs and communication structures, rather than anything resembling a law.

Nevertheless, in the 47 years since computer scientist Melvin Conway inadvertently entered the techie lexicon, there have been various attempts at deriving causal principles from the law. And while causal relationships between our organizations and the software systems they create have plenty of examples, the true causal story – the why of such correlations – has largely escaped us.

That is, until now.

Party Like It’s 1967

zapposRemember that Conway came up with his law in 1967, where newfangled software organizational concepts like Agile and Lean were little more than a gleam in his eye. Instead, his context was the traditional command and control lines of communication within a standard hierarchical organization.

Within such hierarchical organizations, the fundamental difference between one twenty-person team and four five-person teams, for example, are the differing decision making and enforcement structures.

Regardless of whether we have one large or four smaller teams, the resulting systems will clearly follow Conway’s Law – with the one large team creating a single system design, while the four smaller teams will end up producing modular, differing system designs.

When we look at the relationship between our software and our organizational structures within the context of digital and devops transformations, however, the Conway’s Law causal story gets decidedly murkier.

As I explained in the previous Cortex, the diversity within the continuous development, test, integration, and delivery toolchains that devops efforts use would contraindicate the cross-organizational cultural shift that devops represents.

Only if we recognize that the broader open source community is largely responsible for such toolchains, then we can look to the decision making structure of that community at large to indicate why such toolchains have a chance of working together properly. After all, only when our technology works as an integrated whole will Conway’s Law give us hope that we’ll be able to achieve the cultural change we desperately desire within our own organizations.

So too with digital transformation. If we take too narrow a view, perhaps focusing only on the fact that customers are demanding mobile interactions with companies, then Conway’s Law would suggest that the modularization of our system design around mobile technology will cause us to build mobile teams separate from other teams within the digital initiative.

Taking this modularized approach to digital initiatives, however, is a recipe for failure, as this view shortchanges the true nature of digital transformation. But many enterprises are falling into this trap nevertheless, as Conway’s Law would predict.

Self-Organization: The Missing Piece of the Puzzle
However, customers aren’t simply demanding mobile experiences. In reality, they desire omnichannel experiences – interactions with companies that cut across technology touchpoints and form factors to support coherent, long-term relationships – or customer journeys in digital marketing parlance.

Ideally, such omnichannel customer demand should drive crosscutting technology architectures, which in turn should drive crosscutting digital reorganizations. But if we understand Conway’s Law in terms of traditional command-and-control communication structures, we’ll inevitably end up with siloed technology that reinforces rather than breaks down our siloed organizations.

If we do away with such hierarchical thinking, however, an amazing thing happens. People will organize themselves into teams (if you even want to call them teams). Such self-organization, in fact, is behind the success of open source-driven devops toolchains.

The open source community at large is primarily self-organized, as individuals decide where and how to participate, based upon individual priorities and the priorities of the various projects – not 100%, as sometimes external forces drive the organization of such teams, but the community is sufficiently self-organized for sufficiently integrated toolchains to emerge.

Self-organization is also the key to digital transformation. If people self-organize around customer omnichannel priorities, then they will form cross-organizational communication structures that will drive end-to-end system architectures, as Conway’s Law predicts – but only in the presence of such self-organization.

Self-organization alone, however, is not a panacea. After all, in an environment of highly modular software, people are likely to organize by technical specialty around each package. To complement self-organization, therefore, we must introduce the appropriate constraints.

Such constraints should always include the strategic business priority, and should also include necessary governance and security limitations that any team, self-organized or not, must adhere to.

Perhaps the most important effect that establishing this model of self-organization within the context of external constraints is its fundamental adaptability. The constraints can be as dynamic as the situation requires, and people will naturally organize or reorganize as necessary to comply with those constraints – in marked contrast to the inflexibility of traditional command-and-control organizational structures.

Self-Organization, Emergence, and Complex Adaptive Systems
Self-organization within the context of external constraints isn’t a new idea – how Netflix delivers innovation and resilience is one example, and Zappos’ holacracy is another. But without a solid justification for such cutting-edge organizational models, enterprises rightly see them as little more than experiments.

Conway’s Law helps us move past this experimental context for self-organization. Once we have such inherently adaptable organizational structures, we will necessarily end up with inherently adaptable system architectures – the Agile Architecture I’ve been discussing in my research for years.

But most significantly, the shift from command-and-control to self-organization finally shines a light on the why of Conway’s Law: emergence.

The causal pieces to this story only fall into place once we realize the entire enterprise – people as well as technology – form a complex adaptive system. Depending on the constraints that govern the behavior and interaction of our component subsystems (the humans and their software), different emergent behaviors result – emergent in the formal sense of a property of a complex system that isn’t a property of its subsystems.

Furthermore, the nature of emergence explains Conway’s Law – giving us the answer to our basic why question, just as emergence explains why bees create hexagonal hive structures or why many galaxies are spirals.

And we can rest assured that Conway’s Law applies across the full spectrum of subsystem constraints, with traditional command-and-control at one extreme, and fully self-organizing teams at the other. Change the constraints, change the emergent behaviors.

The Intellyx Take: Turning the Agility Dial
In fact, we now have new insight into the usefulness of Conway’s Law, as it helps us understand how to turn the business agility dial on our organizations.

Do we want highly controlled, predictable behavior, well-suited for optimizing traditional business metrics? Turn the dial toward the traditional command-and-control we find in most enterprises today – but don’t be surprised if the systems we end up building are inflexible at best or fully dysfunctional at worst.

On the other hand, if we turn our dial toward self-organization, we’ll end up with technology systems that cut across now-defunct organizational silos, responding to changing business priorities and supporting strategic innovation goals.

A desirable outcome to be sure – but easier said than done, as we must relinquish our preconceptions about how to run a business. Are you ready?

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: Erica Joy.

Read the original blog entry...

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.