A Research Study into DevOps bottlenecks

We asked a Fortune 500 software delivery leaders what holds them back. This talk is the analysis of their insights on what bottlenecks they encountered in their DevOps journey. We share discoveries on what helped them to overcome the bottlenecks and how they plan to deliver even faster. Using this we define some unifying themes on what areas provide the greatest return in investments of time and resources.


Outline/Structure of the Talk

1. how release cadence is relevant to DevOps

2. what is the right release cadence?

3. what holds teams back?

Learning Outcome

why releasing fast is critical to devops and how to achieve it overcoming the most common bottlencks

Target Audience

software engineers

schedule Submitted 1 year ago

  • Liked JBaruch

    JBaruch - #DataDrivenDevOps

    Head of Developer Relations
    schedule 1 year ago
    Sold Out!
    45 Mins

    Devops is usually viewed from a traditional perspective of a collaboration of Dev, Ops, and QA, driven by the change in Culture, People, and Process. But how do you know where you stand and where to move? As in almost any field, data and metrics give you the gauges and instruments. In this talk, we’ll talk about the key measurements for the DevOps transformation process and provide you with 3 metrics you can start measuring tomorrow.

  • Liked Lim Yang Wei

    Lim Yang Wei - To DevOps, or not, it's all about Trust, Freedom and Responsibility

    20 Mins

    In our team, the thing that we valued most is how our codes are making impact to business. It can be deploying feature that create new profit, fixing bug, increasing deployment time and etc.

    Making impact means in the end codes have to be deployed to production. We never set rules related to deployment. Anyone, anytime, anywhere. We even do have so-called "First day deployment" operation which make sure new member make their first deployment to production within 24 hours since they join our team. How do we make sure that works ? We trust. In our team, everyone is AWS admin from the first day. We want make sure everyone has the essential tools to setting up infrastructure, coding, releasing, monitoring. Human being, when given trust they take full responsibilities. Responsibility to complete work and hence making impact to business.

    It sounds like psychology, right ? Or I will just say culture.

    In the end, it's all about trust, freedom and responsibility. Let me show you how and why we inject (or being injected) these cultures into our team, how we improve and make sure it's getting better.

  • Liked Matty Stratton

    Matty Stratton - The Psychology of Chaos Engineering

    45 Mins

    Chaos Engineering, failure injection, and similar practices have verified benefits to the resilience of systems and infrastructure. But can they provide similar resilience to teams and people? What are the effects and impacts on the humans involved in the systems? This talk will delve into both positive and negative outcomes to all the groups of people involved - including users, engineers, product, and business owners.

    Using case studies from organizations where chaos engineering has been implemented, we will explore the changes in attitude that these practices create. This talk will include a brief overview of chaos engineering practices for unfamiliar members of the audience, but the main focus will be on human elements. I will discuss successful implementations, as well as challenges faced in teams where chaos was a “success” from a technical perspective, but contained negative impact for the people involved.

    After seeing this talk, attendees will have a better understanding of the human factors involved in chaos engineering, good practices to care for the people and teams working with chaos, and be even more excited about this practice.