Welcome!

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

Related Topics: @DevOpsSummit, Microservices Expo, Linux Containers

@DevOpsSummit: Blog Feed Post

Adopting DevOps – Overcoming ‘Cultural Inertia’ By @sd_architect | @DevOpsSummit #DevOps

Part V: The organization can only succeed at adopting the DevOps culture if it's able to overcome the inherent Cultural Inertia

Adopting DevOps - Part V: Overcoming ‘Cultural Inertia'

Last month, my partners in crime – Carmen DeArdo from Nationwide, Lee Reid, my colleague from IBM and I wrote a 3-part series of blog posts on DevOps.com. We titled our posts the Simple Math, Calculus and Art of DevOps. I would venture to say these are must-reads for any organization adopting DevOps. We examined all three ascpects – the Cultural, Automation and Process improvement side of DevOps. One of the key underlying themes of the three posts was the need for Cultural change – things like trust, collaboration, communication, etc. I will elaborate more on these soon.

On a persona note, reading Carmen and Lee’s posts and writing my own gave me an opportunity to reflect on the conversations I have been having with executives of late, in organizations across the world, as I work with them to help their organizations adopt DevOps. Irrespective of the size or the organization, the industry, or the geography, these conversations keep going back over and over again to the need to address five areas I alluded to in my post:

  1. Reduce batch size
  2. Shift-left Operational engagement
  3. Continuous funding
  4. Create a ‘Product Management’ team
  5. Setting up a DevOps Center of Excellence (CoE)

These are areas that you as an organization will need to address in order to maximize the benefits of DevOps for you. These are not in the typical domain of process improvement and automation that one sees in the DevOps literature over and over again. The ‘Continuous-es’ we all talk about – Continuous Integration, Continuous Delivery, Continuous Testing, Continuous Feedback, etc, – are not enough to get full value of DevOps. These particular areas are specifically focused on the things organizations need to do on the ‘foundational’ side of how they operate to enable the fostering of a true organization-wide DevOps culture.

Cultural Inertia
At the end of the day, even after all the process improvement and automation that can be introduced in an organization, the organization can only succeed at adopting the culture of DevOps if it is able to overcome the inherent Cultural Inertia. Organizations have inertia – an inherent resistance to change. Change is not easy, especially in large organizations where the cultural may have had years to develop and permeates across hundreds, if not thousands of practitioners. These practitioners, as individuals, may appreciate the value of adopting DevOps, but as a collective resist change and hence have inertia. Overcoming this inertia is key.

How is this inertia exhibited? ‘This is the way we do things here’; ‘Yes, but changing X is not in my control’; ‘You will need to talk to Y about that; WE cannot change how THEY work’… are just some examples of phrases and behaviors that are symptomatic of cultural inertia. Over years, organizations develop behaviors; teams and groups divide up actions and responsibilities along organizational lines; ‘checks and balances’ get established in the name of governance, which are not related to true governance at all; Processes exist but no one know why – they are ‘just there’; reports get produced that no one ever reads any more, but no one is willing to do away with; bad things happened the past and resulted in approval requirements to ensure they never happen again; and so on. All build up Inertia in an organization’s Culture.

Identifying inefficient Artifacts and Processes:
Overcoming Cultural Inertia requires a serious look at each and every artifact and process that may cause the organization to be become inefficient. The way to identify these and then develop a plan to address the inefficiency they cause, is by conducting a ‘Value Stream Mapping’ exercise. A Value Stream Mapping is a ‘Lean’ approach to examine artifacts and processes that different stakeholders in an organization work on to deliver a business capability. In the context of DevOps, this would be for a Delivery Pipeline. A Value Stream Mapping for DevOps hence is a mapping of the Delivery Pipeline to identify which processes may be inefficient, and which artifacts do not add value to the real deliverables of the delivery pipeline. For example, processes may include manual steps such as ticket creation that is a highly inefficient way to hand-off artifacts to another team. They may result in unnecessarily long wait-times as practitioners wait for approvals or actions from other practitioners may not even be on the same timeline. Artifacts may get created, which are not consumable by those who need the information in them. Artifacts may get created that add no value to the final deliverables, such as reports for executives outside of decision makers. Too much data is collected, that is never made available in the right form by decision makers (this actually happens more often than the reverse, that is too little data).

The goal is to identify these ‘bottlenecks’ in the delivery pipeline – inefficient processes, artifacts that can be removed /replaced, wait-times, unnecessary approvals, etc. Once these bottlenecks have been identified, then DevOps practices that can be adopted to help address each of them can be identified for adoption. In most cases there are multiple bottlenecks that get identified and will need to be prioritized before addressing to first address those that have the most return on investment and impact on efficiency, when addressed.

Addressing these bottlenecks require change beyond just traditional DevOps practices. Changes such as reducing batch size, or shifting left operational engagement, require more effort than adopting a tool to enable ‘Automated Delivery’. I would argue that DevOps capabilities like Continuous Delivery cannot be adopted effectively, and will certainly not deliver at its full potential value, unless adopted with mechanisms to address Cultural Inertia.

Do ‘Follow’ my blog and follow me on Twitter to get updates on this series and other upcoming posts.

Related Posts:

Understanding DevOps:

Adopting DevOps:

Read the original blog entry...

More Stories By Sanjeev Sharma

Sanjeev is a 20-year veteran of the software industry. For the past 18 years he has been a solution architect with Rational Software, an IBM brand. His areas of expertise include DevOps, Mobile Development and UX, Lean and Agile Transformation, Application Lifecycle Management and Software Supply Chains. He is a DevOps Thought Leader at IBM and currently leads IBM’s Worldwide Technical Sales team for DevOps. He speaks regularly at conferences and has written several papers. He is also the author of the DevOps For Dummies book.

Sanjeev has an Electrical Engineering degree from The National Institute of Technology, Kurukshetra, India and a Masters in Computer Science from Villanova University, United States. He is passionate about his family, travel, reading, Science Fiction movies and Airline Miles. He blogs about DevOps at http://bit.ly/sdarchitect and tweets as @sd_architect

@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...
"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.
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...
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...
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...
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...
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...