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

You Are Not a DevOp

You Are Not a DevOp

With titles and groups like "DevOps Engineer", "Director of DevOps", "DevOps Team", clearly, DevOps is a thing. But can you really be a DevOp?
In this talk we'll explore some of the history and meaning of DevOps, what it means to "do the DevOps" and how you an take the first steps toward transforming your organization into one that uses DevOps practices to delight your customers.

Originally presented at LOPSA-East 2014

Nathen Harvey

May 03, 2014
Tweet

More Decks by Nathen Harvey

Other Decks in Technology

Transcript

  1. Nathen Harvey •  Community Director, Chef •  Co-host of the

    Food Fight Show Podcast •  DevOpsDC Meetup Organizer •  @nathenharvey •  [email protected]
  2. DevOps •  Cultural and professional movement •  Development and Operations

    working together toward a common goal •  Leveraging ideas & processes from other industries •  Enabling things like continuous delivery
  3. The Backoffice Becomes The Front Office •  “In ten years,

    I’m certain every COO worth their salt will have come from IT. Any COO who doesn’t intimately understand the IT systems that actually run the business is just an empty suit, relying on someone else to do their job.” Kim, Gene; Behr, Kevin; Spafford, George (2013-01-10). The Phoenix Project: A Novel About IT, DevOps, and Helping Your Business Win IT Revolution Press. Kindle Edition
  4. DevOps Culture •  Open Communication •  Incentive and Responsibility Alignment

    •  Respect •  Trust Walls, Mandi (April, 2013). Building a DevOps Culture. O’Reilly http://oreilly.com/radarreports/building-devops- culture.csp
  5. DevOps Tools •  Version Control Systems •  Packaging •  Configuration

    Management •  Continuous Integration •  Game Day Drills •  Incident Management •  Post Mortems
  6. Which Version Control System Do You Use? •  cp foo

    foo.bak •  cp foo{,.`date +%Y%m%d%H%M`}
  7. Which Version Control System Do You Use? •  cp foo

    foo.bak •  cp foo{,.`date +%Y%m%d%H%M`-`$USER`}
  8. Use Tools that Reflect & Reinforce Your Culture •  Open

    Communication •  Incentive and Responsibility Alignment •  Respect •  Trust •  Version Control Systems
  9. Use Tools that Reflect & Reinforce Your Culture •  Open

    Communication •  Incentive and Responsibility Alignment •  Respect •  Trust •  Post Mortems
  10. DevOps •  Cultural and professional movement •  Development and Operations

    working together toward a common goal •  Leveraging ideas & processes from other industries •  Enabling things like continuous delivery
  11. Making DevOps Work •  Strong cultures of personal empowerment and

    accountability •  Treat failure as a learning opportunity, not as a dangerous thing to be avoided •  Web-oriented architectures •  Allergy to things that make you slow •  Addicted to data
  12. To Do •  Put dev and ops in the same

    room •  Take a whole-systems view of your technology platform •  Reinforce culture with technology, and vice versa •  Take responsibility •  Trust your teammates
  13. To Stop Doing •  Mislabeling things •  Hoarding information • 

    Looking for someone to blame •  Waiting for someone else to transform your business
  14. By 2017 Web-Scale IT Will Be an Architectural Approach Found

    Operating in 50% of Enterprises •  The influence of DevOps on IT culture, tools, processes and organizational structure is resulting in the acceleration of application delivery and an environment of continuous experimentation. •  Combining new software architectures with DevOps-style approaches can become the catalysts to improve an IT organization's ability to adapt to change. http://www.gartner.com/newsroom/id/2675916
  15. By 2017 Web-Scale IT Will Be an Architectural Approach Found

    Operating in 50% of Enterprises •  Historically, enterprise IT has been focused on managing risk... However, the major DevOps underpinnings...are enabling these same enterprises to realize they can be fast and 'safe.' Embracing risk is not as risky as it sounds with a DevOps mindset. Having the architecture of the application being more resilient in the first place enables IT operations teams to implement and support leaner and more agile processes that might otherwise be viewed as inappropriate for conservatively minded organizations. http://www.gartner.com/newsroom/id/2675916