Welcome!

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

Related Topics: @DevOpsSummit, Microservices Expo, @CloudExpo

@DevOpsSummit: Blog Post

Spread the DevOps Virus in Your Organization (Part One) By @TheEbizWizard | @DevOpsSummit #DevOps

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

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
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 Cortex - don'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.

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
The nature of test environments is inherently temporary—you set up an environment, run through an automated test suite, and then tear down the environment. If you can reduce the cycle time for this process down to hours or minutes, then you may be able to cut your test environment budgets considerably. The impact of cloud adoption on test environments is a valuable advancement in both cost savings and agility. The on-demand model takes advantage of public cloud APIs requiring only payment for t...
"Codigm is based on the cloud and we are here to explore marketing opportunities in America. Our mission is to make an ecosystem of the SW environment that anyone can understand, learn, teach, and develop the SW on the cloud," explained Sung Tae Ryu, CEO of Codigm, 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.
High-velocity engineering teams are applying not only continuous delivery processes, but also lessons in experimentation from established leaders like Amazon, Netflix, and Facebook. These companies have made experimentation a foundation for their release processes, allowing them to try out major feature releases and redesigns within smaller groups before making them broadly available. In his session at 21st Cloud Expo, Brian Lucas, Senior Staff Engineer at Optimizely, discussed how by using ne...
Many enterprise and government IT organizations are realizing the benefits of cloud computing by extending IT delivery and management processes across private and public cloud services. But they are often challenged with balancing the need for centralized cloud governance without stifling user-driven innovation. This strategy requires an approach that fundamentally reshapes how IT is delivered today, shifting the focus from infrastructure to services aggregation, and mixing and matching the bes...
"CA has been doing a lot of things in the area of DevOps. Now we have a complete set of tool sets in order to enable customers to go all the way from planning to development to testing down to release into the operations," explained Aruna Ravichandran, Vice President of Global Marketing and Strategy at CA Technologies, 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.
While we understand Agile as a means to accelerate innovation, manage uncertainty and cope with ambiguity, many are inclined to think that it conflicts with the objectives of traditional engineering projects, such as building a highway, skyscraper or power plant. These are plan-driven and predictive projects that seek to avoid any uncertainty. This type of thinking, however, is short-sighted. Agile approaches are valuable in controlling uncertainty because they constrain the complexity that ste...
Cavirin Systems has just announced C2, a SaaS offering designed to bring continuous security assessment and remediation to hybrid environments, containers, and data centers. Cavirin C2 is deployed within Amazon Web Services (AWS) and features a flexible licensing model for easy scalability and clear pay-as-you-go pricing. Although native to AWS, it also supports assessment and remediation of virtual or container instances within Microsoft Azure, Google Cloud Platform (GCP), or on-premise. By dr...
"This all sounds great. But it's just not realistic." This is what a group of five senior IT executives told me during a workshop I held not long ago. We were working through an exercise on the organizational characteristics necessary to successfully execute a digital transformation, and the group was doing their ‘readout.' The executives loved everything we discussed and agreed that if such an environment existed, it would make transformation much easier. They just didn't believe it was reali...
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...
Agile has finally jumped the technology shark, expanding outside the software world. Enterprises are now increasingly adopting Agile practices across their organizations in order to successfully navigate the disruptive waters that threaten to drown them. In our quest for establishing change as a core competency in our organizations, this business-centric notion of Agile is an essential component of Agile Digital Transformation. In the years since the publication of the Agile Manifesto, the conn...
"We're developing a software that is based on the cloud environment and we are providing those services to corporations and the general public," explained Seungmin Kim, CEO/CTO of SM Systems Inc., 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 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...
While some developers care passionately about how data centers and clouds are architected, for most, it is only the end result that matters. To the majority of companies, technology exists to solve a business problem, and only delivers value when it is solving that problem. 2017 brings the mainstream adoption of containers for production workloads. In his session at 21st Cloud Expo, Ben McCormack, VP of Operations at Evernote, discussed how data centers of the future will be managed, how the p...
Enterprises are adopting Kubernetes to accelerate the development and the delivery of cloud-native applications. However, sharing a Kubernetes cluster between members of the same team can be challenging. And, sharing clusters across multiple teams is even harder. Kubernetes offers several constructs to help implement segmentation and isolation. However, these primitives can be complex to understand and apply. As a result, it’s becoming common for enterprises to end up with several clusters. Thi...
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...
DevOps teams have more on their plate than ever. As infrastructure needs grow, so does the time required to ensure that everything's running smoothly. This makes automation crucial - especially in the server and network monitoring world. Server monitoring tools can save teams time by automating server management and providing real-time performance updates. As budgets reset for the New Year, there is no better time to implement a new server monitoring tool (or re-evaluate your current solution)....
We just came off of a review of a product that handles both containers and virtual machines in the same interface. Under the covers, implementation of containers defaults to LXC, though recently Docker support was added. When reading online, or searching for information, increasingly we see “Container Management” products listed as competitors to Docker, when in reality things like Rocket, LXC/LXD, and Virtualization are Dockers competitors. After doing some looking around, we have decided tha...
"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.
The benefits of automation are well documented; it increases productivity, cuts cost and minimizes errors. It eliminates repetitive manual tasks, freeing us up to be more innovative. By that logic, surely, we should automate everything possible, right? So, is attempting to automate everything a sensible - even feasible - goal? In a word: no. Consider this your short guide as to what to automate and what not to automate.
identify the sources of event storms and performance anomalies will require automated, real-time root-cause analysis. I think Enterprise Management Associates said it well: “The data and metrics collected at instrumentation points across the application ecosystem are essential to performance monitoring and root cause analysis. However, analytics capable of transforming data and metrics into an application-focused report or dashboards are what separates actual application monitoring from relat...