SYS-CON MEDIA Authors: Elizabeth White, Liz McMillan, William Schmarzo, Yeshim Deniz, Jason Bloomberg

Blog Feed Post

Spread the DevOps Virus in Your Organization (Part One)

When an organization finally figures out how to get DevOps to work properly, it’s unquestionably a beautiful thing. A team working together at full speed, delivering value to their organizations, while laughing in the face of roadblocks that threaten to impede their progress.

Getting to this point wasn’t easy. We had to learn numerous lessons, many from Agile and Lean and other practices, each of which offered part of the answer. And then the technology itself had to reach a level of maturity, both among the tools themselves as well as the infrastructure. Clearly, DevOps owes much to open source. Not to mention APIs. Cloud computing and virtualization. And software-defined, well, everything.

Even taking into consideration those few but remarkable DevOps success stories – stories that are more frequent every day – the work of DevOps is far from complete.

As enterprises today undergo digital transformation, they become software-driven organizations. But software-driven is somewhat of a misnomer, because software alone is only an enabler – just as software-based tools are not the core of DevOps, but merely DevOps enablers.

In reality, to become software-driven, companies must transform organizationally – and the key to such transformation is self-organization.

What we’re missing, however, is a self-organization playbook. That’s where DevOps can help. Getting DevOps to work means getting self-organization to work. The challenge then becomes spreading the approach beyond the software organization.

For this reason I called for the spread of the DevOps ‘virus’ in my last Cortex newsletter.

We’re not simply taking a page out of the DevOps playbook and applying it to ‘non-software’ teams – assuming it even makes sense to talk about such teams in today’s software-driven world.

The goal, in fact, is more subtle: to leverage DevOps principles as a fundamental mechanism to achieve the organizational change necessary for digital transformation success.

Beyond Two Pizzas

pizzahttp://intellyx.com/wp-content/uploads/2016/02/pizza-220x146.jpg 220w, http://intellyx.com/wp-content/uploads/2016/02/pizza-600x398.jpg 600w, http://intellyx.com/wp-content/uploads/2016/02/pizza.jpg 640w" sizes="(max-width: 431px) 100vw, 431px" />

At the heart of the DevOps culture, of course, is self-organization. Self-organizing teams, after all, are an Agile principle that serves us well today, as is the Lean principle (also familiar from Extreme Programming) that everybody on the team is responsible for everything the team produces.

Put these two basic organizational principles together, and you have the basis for cooperation, empathy, and responsibility. People working together to achieve a common goal is the essence of cooperation. Self-organization and joint responsibility facilitate empathy, since you can’t dump problems on someone else.

Nothing particularly insightful or new so far. The challenge, however, comes when we want to expand all this organizational goodness beyond teams of about eight to ten people – the perennial two-pizza challenge. In other words, how do we scale DevOps culture?

The two-pizza challenge, of course, refers to the adage that you can feed an ideally sized team with two pizzas. Clearly, if a team grows much beyond that point, then the ‘everyone is responsible for everything’ principle breaks down quickly.

How, then, can we spread self-organization more broadly? The key is to understand the primary factor limiting our success with self-organization up to this point: we’ve been assembling self-organizing teams all along.

As long as someone (a manager, say) assigns people to a team, the team’s ability to self-organize has just taken a big hit. Sure, team members can decide how to divide up tasks, who sits with whom, and so on. But there’s only so much self-organizing a team can do when someone has put together the team and given them an assignment.

The first key to spreading the DevOps virus beyond the two-pizza level, therefore, is to allow people to choose their own teams, and to allow teams to choose their own goals.

Cross-Pollination among Self-Organizing Teams

For an organization to be comfortable with such self-organization, people must have an understanding of various needs across the organization so they can best decide which teams they should help with.

There also must be adequate communication and collaboration among people outside of existing teams, so that there can be an interplay between the people on teams looking for additional help and the people who have the time, inclination, and ability to provide that help. I like to call this interplay cross-pollination.

Cross-pollination consists of the following general principles:

  • Anyone can identify a business goal they wish to pursue and seek to assemble a team to achieve that goal. That person, however, must be on the team – it’s strictly against the rules for someone to organize a team they don’t belong to. (Stay tuned for part two of this Cortex for more advice to management.)
  • Some people may participate in more than one team at the same time, since each team doesn’t need all of their time. Everybody on a team won’t be a partial contributor as a rule, but chances are some people on each team will qualify.
  • Some people serve a role on a team for only part of the lifetime of the team. They may find themselves moving from one team to another as those teams need them.
  • Nobody is ‘off limits’ when a team needs help from someone outside the team. Even customers are fair game. If a team thinks they need the help of someone else, they can ask anybody they think might help, or might know someone who can help.

Clearly, suitable social networking tools are essential for empowering cross-pollination. It’s no wonder, therefore, that collaboration and communication tools and techniques are such an important part of digital initiatives today (stay tuned for more insight into this topic in a future Cortexdon’t forget to subscribe!)

Decision Making on Self-Organizing Teams

The basic principle of decision making is for teams to do it for themselves, rather than some manager or other external party doing it for them. Here are the basics:

  • It’s up to the team to decide how they make decisions. Vote of the majority? Possibly. Unanimous consensus? Might be worth a try. Let a leader decide? Perhaps – but note that the team also decides whether they need a leader and if so, who it is. Nobody has a pre-defined leadership position; instead, leaders naturally arise as a part of self-organization.
  • Teams must be willing and able to resolve personal conflicts internally. Any team has the ability to kick someone out – but such an occurrence should be treated as a positive cross-pollination opportunity because it frees someone up to help elsewhere, thus turning a potentially morale-killing event into a positive result.
  • All teams have natural lifetimes. When a team coalesces, they should generally give themselves an expiration date (or tie their dissolution to a particular milestone or other event). They can always decide to change this date if necessary, but the default is for teams to expect to disband, thus freeing members to join other teams.
  • All teams should mind the cadence. In some cases the duration and completion times of various teams’ efforts are independent of each other, but it’s also common for teams to need to coordinate release cycles. Does this recommendation mean that there’s a need for a ‘scrum of scrums’ type coordinating team? Perhaps, perhaps not, as such a team should also self-organize.

The Intellyx Take: Where’s the Automation?

For an article that purports to describe a DevOps virus, there was scant mention of the technology enablers of DevOps. DevOps wouldn’t be DevOps without automation-driven continuous integration and continuous delivery (CI/CD), after all, right?

In fact, without CI/CD, DevOps would never have gotten off the ground, because ops folks would still have their hands full with manual tasks. The reason people could break down the dev/QA/ops silos in the first place is because the tooling freed up everybody to drive QA and ops more as extensions of development than as separate silos.

In other words, technology played an essential role in the evolution of self-organizational principles, helping move them from theory to production-tested reality.

Now it’s time to take the next step. To achieve the full vision of digitally transformed organizations, the maturation of technology and organizational principles must proceed apace. Each one needs the other.

That’s why I call this trend the DevOps virus. This virus is contagious. And we need it to infect the entire organization.

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: jeffreyw.

Read the original blog entry...

More Stories By Jason Bloomberg

Jason Bloomberg is a leading IT industry analyst, Forbes contributor, keynote speaker, and globally recognized expert on multiple disruptive trends in enterprise technology and digital transformation. He is ranked #5 on Onalytica’s list of top Digital Transformation influencers for 2018 and #15 on Jax’s list of top DevOps influencers for 2017, the only person to appear on both lists.

As founder and president of Agile Digital Transformation analyst firm Intellyx, he advises, writes, and speaks on a diverse set of topics, including digital transformation, artificial intelligence, cloud computing, devops, big data/analytics, cybersecurity, blockchain/bitcoin/cryptocurrency, no-code/low-code platforms and tools, organizational transformation, internet of things, enterprise architecture, SD-WAN/SDX, mainframes, hybrid IT, and legacy transformation, among other topics.

Mr. Bloomberg’s articles in Forbes are often viewed by more than 100,000 readers. During his career, he has published over 1,200 articles (over 200 for Forbes alone), spoken at over 400 conferences and webinars, and he has been quoted in the press and blogosphere over 2,000 times.

Mr. Bloomberg is the author or coauthor of four books: The Agile Architecture Revolution (Wiley, 2013), Service Orient or Be Doomed! How Service Orientation Will Change Your Business (Wiley, 2006), XML and Web Services Unleashed (SAMS Publishing, 2002), and Web Page Scripting Techniques (Hayden Books, 1996). His next book, Agile Digital Transformation, is due within the next year.

At SOA-focused industry analyst firm ZapThink from 2001 to 2013, Mr. Bloomberg created and delivered the Licensed ZapThink Architect (LZA) Service-Oriented Architecture (SOA) course and associated credential, certifying over 1,700 professionals worldwide. He is one of the original Managing Partners of ZapThink LLC, which was acquired by Dovel Technologies in 2011.

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), and several software and web development positions.

Latest Stories
In his general session at 21st Cloud Expo, Greg Dumas, Calligo’s Vice President and G.M. of US operations, discussed the new Global Data Protection Regulation and how Calligo can help business stay compliant in digitally globalized world. Greg Dumas is Calligo's Vice President and G.M. of US operations. Calligo is an established service provider that provides an innovative platform for trusted cloud solutions. Calligo’s customers are typically most concerned about GDPR compliance, application p...
Kubernetes is a new and revolutionary open-sourced system for managing containers across multiple hosts in a cluster. Ansible is a simple IT automation tool for just about any requirement for reproducible environments. In his session at @DevOpsSummit at 18th Cloud Expo, Patrick Galbraith, a principal engineer at HPE, discussed how to build a fully functional Kubernetes cluster on a number of virtual machines or bare-metal hosts. Also included will be a brief demonstration of running a Galera MyS...
Growth hacking is common for startups to make unheard-of progress in building their business. Career Hacks can help Geek Girls and those who support them (yes, that's you too, Dad!) to excel in this typically male-dominated world. Get ready to learn the facts: Is there a bias against women in the tech / developer communities? Why are women 50% of the workforce, but hold only 24% of the STEM or IT positions? Some beginnings of what to do about it! In her Day 2 Keynote at 17th Cloud Expo, Sandy Ca...
Two weeks ago (November 3-5), I attended the Cloud Expo Silicon Valley as a speaker, where I presented on the security and privacy due diligence requirements for cloud solutions. Cloud security is a topical issue for every CIO, CISO, and technology buyer. Decision-makers are always looking for insights on how to mitigate the security risks of implementing and using cloud solutions. Based on the presentation topics covered at the conference, as well as the general discussions heard between sessio...
New competitors, disruptive technologies, and growing expectations are pushing every business to both adopt and deliver new digital services. This ‘Digital Transformation’ demands rapid delivery and continuous iteration of new competitive services via multiple channels, which in turn demands new service delivery techniques – including DevOps. In this power panel at @DevOpsSummit 20th Cloud Expo, moderated by DevOps Conference Co-Chair Andi Mann, panelists examined how DevOps helps to meet the de...
Fact: storage performance problems have only gotten more complicated, as applications not only have become largely virtualized, but also have moved to cloud-based infrastructures. Storage performance in virtualized environments isn’t just about IOPS anymore. Instead, you need to guarantee performance for individual VMs, helping applications maintain performance as the number of VMs continues to go up in real time. In his session at Cloud Expo, Dhiraj Sehgal, Product and Marketing at Tintri, sha...
According to Forrester Research, every business will become either a digital predator or digital prey by 2020. To avoid demise, organizations must rapidly create new sources of value in their end-to-end customer experiences. True digital predators also must break down information and process silos and extend digital transformation initiatives to empower employees with the digital resources needed to win, serve, and retain customers.
More and more companies are looking to microservices as an architectural pattern for breaking apart applications into more manageable pieces so that agile teams can deliver new features quicker and more effectively. What this pattern has done more than anything to date is spark organizational transformations, setting the foundation for future application development. In practice, however, there are a number of considerations to make that go beyond simply “build, ship, and run,” which changes how...
In his session at 19th Cloud Expo, Claude Remillard, Principal Program Manager in Developer Division at Microsoft, contrasted how his team used config as code and immutable patterns for continuous delivery of microservices and apps to the cloud. He showed how the immutable patterns helps developers do away with most of the complexity of config as code-enabling scenarios such as rollback, zero downtime upgrades with far greater simplicity. He also demoed building immutable pipelines in the cloud ...
In his keynote at 18th Cloud Expo, Andrew Keys, Co-Founder of ConsenSys Enterprise, will provide an overview of the evolution of the Internet and the Database and the future of their combination – the Blockchain. Andrew Keys is Co-Founder of ConsenSys Enterprise. He comes to ConsenSys Enterprise with capital markets, technology and entrepreneurial experience. Previously, he worked for UBS investment bank in equities analysis. Later, he was responsible for the creation and distribution of life ...
Smart Cities are here to stay, but for their promise to be delivered, the data they produce must not be put in new siloes. In his session at @ThingsExpo, Mathias Herberts, Co-founder and CTO of Cityzen Data, discussed the best practices that will ensure a successful smart city journey.
A look across the tech landscape at the disruptive technologies that are increasing in prominence and speculate as to which will be most impactful for communications – namely, AI and Cloud Computing. In his session at 20th Cloud Expo, Curtis Peterson, VP of Operations at RingCentral, highlighted the current challenges of these transformative technologies and shared strategies for preparing your organization for these changes. This “view from the top” outlined the latest trends and developments i...
When you focus on a journey from up-close, you look at your own technical and cultural history and how you changed it for the benefit of the customer. This was our starting point: too many integration issues, 13 SWP days and very long cycles. It was evident that in this fast-paced industry we could no longer afford this reality. We needed something that would take us beyond reducing the development lifecycles, CI and Agile methodologies. We made a fundamental difference, even changed our culture...
"Space Monkey by Vivent Smart Home is a product that is a distributed cloud-based edge storage network. Vivent Smart Home, our parent company, is a smart home provider that places a lot of hard drives across homes in North America," explained JT Olds, Director of Engineering, and Brandon Crowfeather, Product Manager, at Vivint Smart Home, in this SYS-CON.tv interview at @ThingsExpo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
LogRocket helps product teams develop better experiences for users by recording videos of user sessions with logs and network data. It identifies UX problems and reveals the root cause of every bug. LogRocket presents impactful errors on a website, and how to reproduce it. With LogRocket, users can replay problems.