Welcome!

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

Related Topics: @DevOpsSummit, Microservices Expo, Linux Containers, Containers Expo Blog

@DevOpsSummit: Article

The DevOps Virus | @DevOpsSummit #Agile #DevOps #ContinuousDelivery

Selecting such teams throws a wrench in the entire works, limiting the value of self-organization

Whenever the conversation in a large organization circles around to how to be more innovative, someone always brings up a skunkworks.

According to Wikipedia, the original Skunk Works is Lockheed Martin's Advanced Development Programs (ADP), responsible for the design of several aircraft - an effort that continues to this day.

Over time, however, the term skunkworks has taken on a broader meaning. Innovation thought leader Everett Rogers (the fellow who coined the term early adopter) defined a skunkworks as "an especially enriched environment that is intended to help a small group of individuals design a new idea by escaping routine organizational procedures."

Rogers goes on to point out that "the research and development (R&D) workers in a skunkworks are usually specially selected, given special resources, and work on a crash basis to create an innovation."

For a large organization struggling with rigid hierarchies and the inflexible decision making that characterizes them, spinning off a skunkworks team seems to make sense. Set up a chic office space in a remote location, choose some particularly creative individuals, and tell them to go forth and innovate.

What could possibly go wrong?

If you've been following my research on self-organization, you might be able to discern the problem. When I talk about driving innovation with self-organizing teams, I emphasize that such self-organization includes expecting the participants to organize their own teams, give themselves their own goals, and determine for themselves how to measure their success.

In contrast, Rogers' definition of skunkworks points out that members of such teams are "usually specially selected." Good thing he added the word usually - because specially selecting such teams throws a wrench in the entire works, limiting the value of self-organization and thus the ability for the organization as a whole to become more agile.

The Skunkworks Catch
There are a number of reasons why assigning people to special teams responsible for driving innovation can be counterproductive - what I like to call the skunkworks catch.

First, the individuals in the team may find that their teammates are not their preferred choice for such an effort. Good managers will be familiar enough with the skill sets as well as the personal relationships and work preferences of the people they assign to a skunkworks team, but there's a measure of guesswork for even the best manager - and of course, many are far from being the best.

Perhaps the most significant problem with assigning people to a skunkworks team, however, is what such an assignment does to the morale of their colleagues left behind.

People generally regard getting selected for such a team as a privilege, with a variety of tangential perks as well as the core opportunity to work on something innovative. From the perspective of the other people in the organization, however, they're left with the grunt work - only now, even more grunt work as some of their colleagues had the good fortune to leave such drudgery behind.

Even if we set aside the adverse morale impact of a skunkworks team on the rest of the organization, there's always the real possibility that some of the people left off of the team are also particularly creative, and would thus have some real value to contribute toward developing innovations that move the needle for the business.

Reinventing the Skunkworks
The Agile Digital Transformation approach to building self-organizing teams, in contrast, is to expect individuals to form the teams themselves.

People should approach their work environment overall with a volunteer mindset, keeping their eyes open for better ways to provide value to the business.

If someone thinks they can come up with an innovation - either because they have an idea that might fly or simply because they would like to participate on a skunkworks team - they can chat with their colleagues across the organization and attempt to form such a team.

For organizations that have business agility as a strategic business driver, the role of management in this process is to communicate the strategic goals of the organization, provide the necessary resources, delineate the required constraints (for example, regulatory and security constraints), and then get out of the way.

Once the organization gets up to speed with self-organization, however, managers should no longer assign people to teams, assign tasks to teams, establish goals for teams, or decide on how teams' progress toward their goals should be measured. The people on those teams should take care of those tasks for themselves.

The self-organizing teams that result may decide to tackle various tasks depending upon the goals set out for the organization as a whole. Some such teams will focus on innovation, while others will decide to work on more tactical efforts.

Self-Organizing Beyond the Skunkworks

If you're used to thinking about large organizations in conventional ways - as most people are wont to do, unfortunately - then you're likely to see two problems with my suggestions regarding self-organized skunkworks teams: first, won't everybody jump at being on a skunkworks team, leaving routine work unfinished? And second, won't this whole process lead to a chaotic free-for-all, producing useless innovations that don't align with corporate goals or strategy?

The answer to these two problems is to learn the lesson of the DevOps Virus: self-organization should extend beyond the team level.

As we move to an organizational model consisting of a number of fluid, self-organizing teams, then self-organization will emerge at what we might call the ‘team of teams' level. In other words, if a skunkworks team is getting off-track, where its innovations appear to be misaligned to the goals of the organization, then other teams can decide amongst themselves to interact with the skunkworks team in question in order to bring the errant group back in line.

In other words, just because a team has decided to go the skunkworks route doesn't mean that lines of communication and influence that connect it to other teams are entirely severed. After all, people can still move into and out of teams as they and the teams decide, depending both on their personal preferences as well as the preferences of each team as a whole.

The goal is for all the teams taken together to have a naturally emerging self-correcting process that keeps everyone on track, even as business needs evolve and unexpected innovations change the playing field.

Just as individual teams can self-correct by deciding to eject a member, say, the entire organization can self-correct by influencing wayward teams to get with the program.

The Intellyx Take
By applying the principles of self-organization at both the team level and the team-of-teams level, we're essentially recommending an inclusive approach to skunkworks-based innovation rather than the traditional exclusive approach.

Whenever management imposes a separation on an organization where some people get a perceived benefit that others do not, morale issues quickly form and the end result is counterproductive. This is just as true for innovation as it is for Bimodal IT, where fast, digital teams get the perceived benefit over the poor souls relegated to slow, traditional IT.

In contrast, if the expectation is that people can choose their own teams and teams can choose their own goals, then the organization benefits in two fundamental ways: the morale issue goes away, and furthermore, the fast-moving, creative, innovative aspects of every individual in the organization can be brought to bear not just to drive business velocity and innovation, but to transform those parts of the organization that would otherwise velocity and innovation back.

The one missing piece of this Cortex which will have to wait till a future issue is the question of incentives (click here to subscribe to the Cortex newsletter). Given the freedom to choose their tasks, people will naturally gravitate toward the more interesting ones, and thus other important, but less fulfilling tasks risk getting neglected.

Instituting the appropriate incentives can help to balance this equation. However, traditional incentive strategies frequently go wrong. Agile organizations, therefore, must reinvent their incentive processes and policies as well. Stay tuned!

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: Greg Schechter.

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.