If your job is to make software, you’re probably busy. Everyone needs new features yesterday. Stuff breaks. How do you make time to work smarter? How do you know where you should focus the time you do have for process improvement? In this week, we’ll cover the fundamentals of DevOps and continuous delivery with an emphasis on the relationship between required investment and benefits. (Please note that if you audit this course, only the first module is available and you will not earn a course certificate. You will also need the ability to download PDFs to view all the information in this course.)

Focusing and automating your software testing is one of the most critical foundation elements to a continuous delivery capability. Thinking like a developer and looking at how to automate repetitive tasks is a lot of what DevOps collaboration is about. In this week, we’ll explore the test stack with a focus on the when and how’s of automated testing.

Something like 99% of the code that delivers your functionality to the user is code you don’t write- it’s an operating system and supporting packages from third parties. The quality and availability of standard components has driven down the cost of software development exponentially. It’s also increased the importance of managing this supporting code and the environments where it runs to support your application. In this week, we’ll look at the techniques and tools teams are using to manage their environments and operations for continuous delivery.

You now have an understanding of the key components of a continuous delivery capability. The key to success is focusing on the right things at the right time and creating momentum with your initial investments on the capability. In this final week, we’ll look at how teams get their continuous capability online and keep their pipeline healthy.