Hacking IT Culture
May 04, 2017

Mark Levy
Micro Focus

Culture is an organization's pattern of response to the problems and opportunities it encounters. One of the main principles of DevOps is the creation of a generative, high-trust culture that supports continuous improvement. Without it, you will not move forward and improve as an organization.

Changing to a DevOps culture can be extremely challenging, often leading to disappointment. This is largely because organizational silos between Dev and Ops can be hard to penetrate. The key is to avoid making sweeping changes as successful cultural change happens in the course of the incremental pursuit to this high-trust generative culture.

There is no "right" culture for DevOps, but characteristics such as open communication, high cooperation, collaboration, respect, and trust are essential. These characteristics create a generative environment in which continuous improvement leads to ever-higher levels of throughput and stability. Product teams form and work together through the delivery process, collaborating on ways to reduce the cost and risk of making changes. Risks and goals are shared, bridging is encouraged, and failure is treated as a learning opportunity.

If your organization does not have these characteristics, they must be developed. Culture is learned, not inherited. It must be genuinely nurtured by everyone from executive management on down the line. Here are some hacks to help develop a positive DevOps culture.

Leadership Sets the Tone

Culture needs to be treated like any other business initiative. Someone needs to own it and leadership must be on board. The DevOps transformation will need people, budget, and time. People may need to be moved and workloads may change. The goals and objectives need leadership buy in to ensure everyone is on the same page. Executives should realize that significant change is necessary since current delivery processes are failing to meet the needs of the business. If management is not on board, it's a warning sign that your company may be heading into obsolescence.

Pick the Right Team and Start Small

If DevOps is new to you, it's important to start out small. DevOps culture might not feel natural at first, so you need a place to practice. Start with a single product team and fully commit, so you can flush out any issues early on. Starting small is less expensive, is not seen as a threat, and can initially be classified as an experiment. Pick a team that is open to experimentation and change. While teams working with modern platforms seem to be the logical first choice, quite often teams working on legacy apps would jump at the chance.

Develop Respect and Trust

Developing respect and trust within the team is critical. Respect begins with common courtesy, but extends beyond simply being polite to a culture where people are truly valued for their individual worth. Respect people's time during work and more importantly during off hours. Keep meetings to an absolute minimum or eliminate them altogether. Email or messages outside work hours are taboo unless you have a good reason.

Build trust with open, transparent, bi-directional communication. Treat feedback as a gift and make sure it's addressed. Ensure the team has access to all the necessary information and empower them to make decisions. Create a safe environment for the team to experiment and learn. Failure leads to inquiry. These hacks breed trust, save time, and accelerate decision-making.

Get Everyone on the Same Page

Have a clear set of goals and measurable outcomes. Make sure everyone on the team has the same priorities. Remove the conflicting incentives between Dev and Ops so that everyone is pushing in the same direction. Developers should be on call to support deployments. Operations should be in sprint reviews and retrospectives. Everyone is responsible for reducing cycle times as well as improving quality. Everyone should be focusing on delivering customer value faster with less risk.

Automate, Automate, Automate

Tools and processes influence culture. Provide self-service provisioning and automate deployments. Make delivering software a non-event and watch innovation soar and a generative culture grow.

Spreading DevOps Culture

There are several options for spreading the culture: split and seed a new team, grow the existing team and then split it into new teams, or use internal coaching to transform other teams to a DevOps culture. Make sure to communicate successes and whenever possible, tell the story with data. Make the DevOps culture visible to the world.

Even in the best environments, shaping culture to a specific set of attributes can be hard. Cultures are mutable and shift in response to external and internal changes. Find the hacks that mean the most to the organization and be consistent. Work them into the organizational DNA and be patient. Changing people's behaviors and attitudes is harder than changing code but the results will transform IT to a high-performance organization that will meet the demands of the business.

Mark Levy is Director of Strategy, Software Delivery, at Micro Focus.

The Latest

April 24, 2018

Developers and engineering teams are under increasing pressure to release higher quality software faster. Continuous testing has proven to be central to these efforts as it helps eliminate bottlenecks and ensures that automated testing is a constant throughout the development process, not an exercise relegated to the "last mile." The value of automated testing is more evident than ever before, with nearly half the respondents reporting that management is fully committed to automated testing and with plans to increase spending, according to the recent Sauce Labs Testing Trends for 2018 report ...

April 19, 2018

As development speed has become a competitive advantage, the DevOps team has sought to enable continuous integration and continuous delivery (CI/CD). For the CI/CD process to be successful, it must be fast and efficient. Any potential roadblocks that delay any part of the process increase cycle times and slow down delivery ...

April 18, 2018

The top barriers to DevOps adoption involve stagnant organizational cultures; managing the jumble of legacy processes, IT infrastructure and newly created cloud environments; and growing software complexity that impacts application modernization initiatives ...

April 16, 2018

This is the third in a series of three blogs directed at recent EMA research on the digital war room. In this blog, we'll look at three areas that have emerged in a spotlight in and of themselves — as signs of changing times — let alone as they may impact digital war room decision making. They are the growing focus on development and agile/DevOps; the impacts of cloud; and the growing need for security and operations (SecOps) to team more effectively ...

April 12, 2018

Only 52 percent of developers using commercial or open source components in their applications update those components when a new security vulnerability is announced, according to new research conducted by Vanson Bourne for CA Veracode, part of CA Technologies. This highlights organizations' lack of security awareness and puts organizations at risk of a breach ...

April 10, 2018

For a few years now, it has seemed like agile developers and DevOps teams haven't been giving testing its proper due. One could almost picture them thinking, "So what if there's a bug, design flaw or performance issue. We'll fix it in the new version next week." Of course, this line of thinking has turned out to be a big mistake ...

April 09, 2018

Government IT professionals surveyed, as part of F5 Networks' State of Application Delivery report, made it clear they are heavily focused on building the foundation necessary for application-driven digital transformation. Around the world, government organizations are shifting towards digital government, and with that we see government organizations embracing the cloud, adopting automation and orchestration, and adjusting security strategies ...

April 05, 2018

The digital war room — physical, virtual or hybrid — is not in retreat but in fact is growing in scope to include greater participation from development and security. It's also becoming more proactive, with on average more than 30% of "major incidents" before they impacted business service performance. In this blog I'm providing a few additional highlights from the insights we got on digital war room organization and processes ...

April 04, 2018

Many development organizations rely on DevOps, Agile and Continuous Integration/Continuous Delivery (CI/CD) practices and tools to speed up application delivery. However, shorter release cycles and faster application development also mean more frequent database schema and logic changes. Though the application release process has been fast-tracked through modernization and automation, the database deployment process has been forsaken ...

April 02, 2018

As March Madness is well underway, the journey to the NCAA basketball national championship feels much like the journey many organizations are on to achieve business success through digital transformation ...

Share this