Upgrade to Pro — share decks privately, control downloads, hide ads and more …

The Changing Role of Operations

The Changing Role of Operations

The expectations and responsibilities for a modern operations team are high. Today, ops is expected to build and design delivery pipelines, have continuous statistic collection as a part of their monitoring services, and complement the development process with continuous integration and delivery practices, all while still maintaining critical back-office applications that most wouldn’t wish upon their enemies. How did it get that way? What separates the operations teams that lead from the ones who react? To dig in, we’ll consider a reactive team mired in fire-fighting and incapable of making headway, then watch as change that betters the team’s output and perception throughout the organization is slowly introduced. We’ll cover root-cause analysis efforts, bringing pain forward, experimentation, shifting left on quality, and selling automation and DevOps practices to management. This talk will not focus on tools, but rather procedural and cultural improvements that highlight the journey operations has undergone, and how we can prepare for the future.

Michael Stahnke

October 11, 2017
Tweet

More Decks by Michael Stahnke

Other Decks in Technology

Transcript

  1. @stahnma 1. a set of connected things or parts forming

    a complex whole, in particular. 2. a set of principles or procedures according to which something is done; an organized scheme or method.
 
 
 

  2. @stahnma 1. the process or activity of running a business

    or organization 2. the action of dispensing, giving, or applying something.
 
 

  3. @stahnma phones, network, dns, smtp, dhcp, storage, virtualization, clustering, printers,

    directory services, data center layout, bill back, filesystem management, backups, disaster recovery, moving furniture, user management, web servers, disk usage, system upgrades
  4. pipelines, continuous integration, version control practices, deployment strategies, monitoring, statistics,

    metrics, automation tools, automated testing, continuous delivery, security
  5. pipelines, continuous integration, version control practices, deployment strategies, monitoring, statistics,

    metrics, automation tools, automated testing, continuous delivery, security phones, network, dns, smtp, dhcp, storage, virtualization, clustering, printers, directory services, data center layout, bill back, filesystem management, backups, disaster recovery, moving furniture, user management, web servers, disk usage, system upgrades
  6. pipelines, continuous integration, version control practices, deployment strategies, monitoring, statistics,

    metrics, automation tools, automated testing, continuous delivery, security phones, network, dns, smtp, dhcp, storage, virtualization, clustering, printers, directory services, data center layout, bill back, filesystem management, backups, disaster recovery, moving furniture, user management, web servers, disk usage, system upgrades and
 others
 … and
 others
 …
  7. pipelines, continuous integration, version control practices, deployment strategies, monitoring, statistics,

    metrics, automation tools, automated testing, continuous delivery, security phones, network, dns, smtp, dhcp, storage, virtualization, clustering, printers, directory services, data center layout, bill back, filesystem management, backups, disaster recovery, moving furniture, user management, web servers, disk usage, system upgrades and
 others
 … and
 others
 …
  8. @stahnma CONSTANTS • There is no bubble • The building

    blocks (primitives) evolve, but always exist • There is always tech to manage • Automation is how we scale • Capabilities more important than technologies