The Wayback Machine - https://web.archive.org/web/20180221213110/http://devops.sys-con.com/node/4098972

Welcome!

@DevOpsSummit Authors: Pat Romanski, Elizabeth White, Liz McMillan, Stackify Blog, Dana Gardner

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

@DevOpsSummit: Blog Post

The Four Core Capabilities of #DevOps | @DevOpsSummit #Serverless #CloudNative

These capabilities are the main levers for improving software

The Four Core Capabilities of DevOps
By Necco Ceresani

DevOps is good for organizations. According to the soon to be released State of DevOps Report high-performing IT organizations are 2X more likely to exceed profitability, market share, and productivity goals. But how do they do it? How do they use DevOps to drive value and differentiate their companies?

We recently sat down with Nicole Forsgren, CEO and Chief Scientist at DORA (DevOps Research and Assessment) and lead investigator for the State of DevOps Report, to discuss the role of measurement in DevOps Success. From years of research into DevOps operations and culture, Forsgren and her colleagues have found that success depends on improving two key outcomes—speed and stability. These, she says, are crucial for driving improvement in organizational performance and value.

But achieving these outcomes requires investing in certain core capabilities. These capabilities, which fall into four broad categories, are the main levers for improving software and, in turn, driving, predicting and positively impacting an organization’s bottom line.

Technology and Automation
Improvement in any of these areas within the Technology & Automation category will have fantastic down-the-road effects on your ability to develop and deliver software. Key capabilities include:

  • Using version control for all production artifacts
  • Automating your deployment process
  • Implementing continuous integration
  • Using trunk-based development methods
  • Implementing test automation
  • Supporting test data management
  • Shifting left on security
  • Implementing Continuous Delivery

The most challenging item on this list, says Forsgren, is supporting test data management, while the highest performing companies tend to be strongest in the automation of their deployment process. If you’re just getting started with your DevOps Journey, Forsgren recommends starting with version control for all production artifacts.

Management and Process
To improve in the areas of management and process, Forsgren suggests starting with the following capabilities:

Gathering, Implementing and Broadcasting Customer Feedback—Does your development team know why they’re coding what they’re coding? Are you gathering ideas about what you should code directly from your customers? Does your development team know where suggestions come from?

Making the Flow of work visible throughout the value stream—This capability goes beyond just having dashboards. It’s about making the value flow visible and allowing people to understand where their piece fits into the whole flow.

Working in small batches and having a lightweight approval process—This helps ensure work can get through the system very quickly.

Measurement and Monitoring
This category prescribes four key capabilities for driving improvement:

  • Monitoring Across Application and Infrastructure to inform Business Decisions. (Note that, while many companies are good at monitoring across workflow, they’re not as good at using that information to inform business decisions.)
  • Checking System Health Proactively
  • Improving Processes and Manage Work with WIP Limits
  • Visualizing Work to Monitor Quality and Communicate—Think dashboards that are very visible and accessible!

Culture
Culture is one of the more difficult areas for companies to improve. But by gaining a better understanding of the capabilities that enable strong DevOps cultures, they can start laying the foundation for a healthy and successful IT organization. These capabilities are:

Encouraging and supporting learning – Taking seriously the value in learning, understanding it as an investment instead of a short-term cost.

Supporting and facilitating collaboration among teams

Providing resources and tools that make work meaningful – This capability goes way beyond “job satisfaction,” which is a shallow measure how happy people are with what they do. It’s about whether people find meaning in their work and are given the resources and tools they need to succeed.

Supporting a “generative” culture – We typically think of DevOps culture in terms of things like communicating across silos or implementing new ideas. Forsgren explains, however, that companies need a solid framework to predict performance outcomes and understand why things go wrong. For that, she and her fellow researchers borrowed from sociologist Ron Westrum, who created a model for predicting and understanding success outcomes in high-risk, highly complex fields like healthcare, aviation, and nuclear power.

This framework also works well for understanding the cultural characteristics that affect performance in technology companies. Forsgren notes that high performing technology organizations are more likely to encourage generative cultures.

Take a look at the table below. Do you know where your company falls? Does it spur ideas about how your organization might make cultural changes that would improve software delivery?

To continue learning about the role measurement within DevOps Success and our entire conversation with Nicole Forsgren click here.

The post The 4 Core Capabilities of DevOps appeared first on XebiaLabs.

Read the original blog entry...

More Stories By XebiaLabs Blog

XebiaLabs is the technology leader for automation software for DevOps and Continuous Delivery. It focuses on helping companies accelerate the delivery of new software in the most efficient manner. Its products are simple to use, quick to implement, and provide robust enterprise technology.

@DevOpsSummit Stories
ChatOps is an emerging topic that has led to the wide availability of integrations between group chat and various other tools/platforms. Currently, HipChat is an extremely powerful collaboration platform due to the various ChatOps integrations that are available. However, DevOps automation can involve orchestration and complex workflows. In his session at @DevOpsSummit at 20th Cloud Expo, Himanshu Chhetri, CTO at Addteq, will cover practical examples and use cases such as self-provisioning infrastructure/applications, self-remediation workflows, integrating monitoring and complimenting integrations between Atlassian tools and other top tools in the industry.
"Storpool does only block-level storage so we do one thing extremely well. The growth in data is what drives the move to software-defined technologies in general and software-defined storage," explained Boyan Ivanov, CEO and co-founder at StorPool, in this SYS-CON.tv interview at 16th Cloud Expo, held June 9-11, 2015, at the Javits Center in New York City.
Is advanced scheduling in Kubernetes achievable?Yes, however, how do you properly accommodate every real-life scenario that a Kubernetes user might encounter? How do you leverage advanced scheduling techniques to shape and describe each scenario in easy-to-use rules and configurations? In his session at @DevOpsSummit at 21st Cloud Expo, Oleg Chunikhin, CTO at Kublr, answered these questions and demonstrated techniques for implementing advanced scheduling. For example, using spot instances and cost-effective resources on AWS, coupled with the ability to deliver a minimum set of functionalities that cover the majority of needs – without configuration complexity.
As Marc Andreessen says software is eating the world. Everything is rapidly moving toward being software-defined – from our phones and cars through our washing machines to the datacenter. However, there are larger challenges when implementing software defined on a larger scale - when building software defined infrastructure. In his session at 16th Cloud Expo, Boyan Ivanov, CEO of StorPool, provided some practical insights on what, how and why when implementing "software-defined" in the datacenter.
A strange thing is happening along the way to the Internet of Things, namely far too many devices to work with and manage. It has become clear that we'll need much higher efficiency user experiences that can allow us to more easily and scalably work with the thousands of devices that will soon be in each of our lives. Enter the conversational interface revolution, combining bots we can literally talk with, gesture to, and even direct with our thoughts, with embedded artificial intelligence, which can process our conversational commands and orchestrate the outcomes we request across our personal and professional realm of connected devices.