YOW! CTO Summit 2019 Melbourne Day 1

Wed, Dec 11
Timezone: Australia/Melbourne (AEST)
08:00

    Registration for YOW! CTO Summit Melbourne 2019 - 45 mins

08:45

    Session Overviews and Introductions - 15 mins

09:00
09:35
10:10
10:40

    Morning Tea - 30 mins

11:10
11:45
  • Added to My Schedule
    keyboard_arrow_down
    YOW! Conference

    YOW! Conference - Lean Coffee

    schedule  11:45 AM - 12:45 PM place Grand Ball Room 1 star_halfRate

    From leancoffee.org: Lean Coffee is a structured, but agenda-less meeting. Participants gather, build an agenda, and begin talking. Conversations are directed and productive because the agenda for the meeting was democratically generated. The format for a Lean Coffee is intentionally very simple. It is meant to be the least structure necessary for a coherent and productive meeting.

    Ideas are generated individually, then pooled with those on your table to be then grouped, voted on, and discussed in a timebox. Detailed instructions and explanations will be provided on the day and we will have a few experienced facilitators handy to make sure things run smoothly.

    This session will be a great opportunity to dig deeper into those "aha" moments or questions that arose from the morning's talks, and discuss your current challenges or ideas with your peers at the table.

12:45

    Lunch - 60 mins

13:45
  • schedule  01:45 - 02:15 PM place Grand Ball Room 1 star_halfRate

    Aligning to a DevOps culture has seen many organisations gain a distinct competitive advantage in their marketplace - especially if they started changing their thinking early which Seek did. Frequent daily deployments, teams owning what they build, the ability to iterate and deliver Products faster, and a greater emphasis on collaboration with much less of "that's not my job", has achieved many benefits. But there is flipsides to this rapid rate of change, and depending on your perspective, how you capitalise on it could be the next big advantage you can take.

    When teams gain greater autonomy to make technology choices the amount of diversification in your enterprise grows rapidly - especially when you are on the bleeding edge of what the major cloud providers are releasing. This increase in diversification will place greater cognitive loads on the people operating and building the system, to a point where an ability to mental model your systems becomes impossible. Incidents and failure will still be a part of normal system functions, still just as complex, but more asynchronous and therefore more difficult to diagnose the reverberations of failure through the system. How you embrace failure in this greater field of diversification, learn from it and use it, is what will set you apart.

    This presentation will discuss how Seek has dealt with and collated extensive amounts of data on "Normal Accidents" over the last several years. We will demonstrate how incident analysis and involvement of teams in post-mortem rituals, has paved the way to many starting viewing our diverse software stack as the Socio-Technical system it is, and how appreciating the "Human Factors" elements of incidents are important to building greater resiliency in the system. We will discuss how involvement of technology people in incident investigation and facilitation will lead to richer amounts of data, that can be fed back into the delivery cycle and continuously improve the reliability and resiliency of your products We will also discuss the traps and pitfalls to avoid such as obsessing over the Root Cause and why the “5 Why’s” technique of incident analysis can be flawed.

14:20
15:20

    Afternoon Tea - 30 mins

15:50
  • Added to My Schedule
    keyboard_arrow_down
    John Viner

    John Viner - Rolling out Error Budgets across a 1000 person global engineering organisation

    schedule  03:50 - 04:20 PM place Grand Ball Room 1 star_halfRate

    Zendesk has been struggling with reliability from it’s beginning - in many ways it has been a victim of its own overnight success. Over the last few years we’ve had to take drastic measures to address major outages, such as implementing company-wide change freezes.

    These measures hurt when you have 1000 engineers in 120 product development teams across the globe, and in many ways create more risk when the freeze begins to thaw.

    In order to avoid these freeze’s we have recently moved to implement concepts from the Site Reliability Engineering (SRE) discipline, specifically implementing Error Budgets along with SLOs/SLIs. The aim of this is to “scope” the freeze to those systems that have more reliability issues.

    We’ve had some wins in introducing this approach, but are still very much at the beginning of this journey. This talk will tell the story of this journey along with providing some practical suggestions around tooling and practices to implement.

16:25
16:55

    Networking Drinks - 60 mins