Description
Course info
Rating
(996)
Level
Beginner
Updated
Jul 28, 2014
Duration
1h 33m
Description

What is DevOps, really? In this course, we look the problems faced by today's IT departments and how a DevOps transformation can help focus on value and streamlined delivery. We'll explore the key cultural changes necessary, where organizational change is required, and how to confront the inevitable objections. Automation and technology play huge roles in DevOps success; in this course we'll analyze the major capability areas and which technologies can get your team on its way.

About the author
About the author

Richard Seroter is a Senior Director of Product for Pivotal, a 10-time Microsoft MVP for cloud/integration, an instructor for developer-centric training company Pluralsight, the lead InfoQ.com editor for cloud computing, and author of multiple books on application integration strategies.

More from the author
More courses by Richard Seroter
Section Introduction Transcripts
Section Introduction Transcripts

Problems That DevOps Solves
Hi, my name is Richard Seroter and welcome to this course on DevOps. We're going to be covering the Big Picture of DevOps, hence the title, really cover what does it mean, what's it all about. For me, I'm the Director of Product Management for a leading cloud provider, CenturyLink, a book author, blogger, frequent trainer for Pluralsight, and a public speaker. So what's the point of this course? Really it's to get an understanding of what DevOps is, what are the principles behind it? How do you realize the actual benefits of it? What are the objections to it from outside parties or even yourself? What are some strategies for implementing this within an organization adopting some of those technologies? So we'll talk about strategy, we'll talk about technology together in a relatively brief course to give you a real good introduction. Whether you're a Developer, Architect, System Administrator, CIO, Project Manager or Business Analyst, really anyone in a technology function there should be something for you here as you try to understand the impact of something like DevOps on your role in an organization. To some extent DevOps feels like the new cloud. Everybody's talking about it, but what is it really? Is it just a rebranding of things we had before? Is it a fad? Is it a set of technologies, a cultural thing? We're going to try to get to the bottom of that.

Making a DevOps Transition
My name is Richard Seroter. Welcome to this second module on the course on DevOps, the Big Picture. The goal of this module is to talk about some of the cultural organizational considerations for adopting a DevOps mindset. So, what do you really need to do set the foundation to properly use technology to actually enact change in an organization? In our last module we really discussed how, to some extent, speed and reliability and things like that that are a competitive advantage. And many organizations struggle with the results of a siloed organization. You end up with waste, you end up with inefficiencies. So, we talked about a fictitious company, Globomatics, and the pain and waste that they faced. We then talked a bit about Lean and DevOps as a way to focus IT on delivering value, kind of setting up this conversation.

Introducing DevOps Automation
Hi, my name is Richard Seroter. Welcome to this third and final module on a course on DevOps, The Big Picture. In this one we're going to bring some things all together and talk about some of the automation components of DevOps. Specifically, we're going to talk about some of the DevOps friendly technologies that complement the cultural changes, organizational changes, that we've talked about in previous modules. What are those things that really start to bring that into focus? If we rewind from the previous modules, we talked about the cultural and the organizational changes needed. We talked through a lot of those. That you can't do technology alone if you don't have the teamwork set up. If you don't have a team structure set up, that even has some of the shared knowledge and some of the system ownership and accountability and empowerment that's necessary. What we're focused on here, on continuous improvement. How am I using technology to continue to help with improvement? I don't like the, if it's not broke, don't fix it mentality. That doesn't work in DevOps. DevOps should be about automating repetitive tasks, the feedback loop between Dev and Ops and other teams, always learning. Just because something's not broke, doesn't mean it's optimized, that there's not tons of waste in it or that it doesn't actually work well in the whole flow of the system. So, we should be constantly looking at improvement and how do we grow? How do we make sure we're doing things in our system? Hopefully often now, using technology to make that possible. The stages of maturity, as you think about this progression of technology, you go from using just source control, and sometimes that's a big step. You might just have source control sitting on a file share somewhere, on your local machine. So even using a centralized source control is a good first step. Then, having builds actually triggered by committing your source control and doing integration testing right there. Then moving into some automated deployment to testing. Have that next step of maturity of actually taking these builds and putting them somewhere. Then actually automating some functional testing and having that baked into your process. And then really getting to this point where you can do continuous deployment to production. So as we talk now about these tools, keep some of that in mind.