Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying DevOps Adoption Strategies: Principles, Processes, Tools, and Trends
  • Table Of Contents Toc
  • Feedback & Rating feedback
DevOps Adoption Strategies: Principles, Processes, Tools, and Trends

DevOps Adoption Strategies: Principles, Processes, Tools, and Trends

4 (11)
close
close
DevOps Adoption Strategies: Principles, Processes, Tools, and Trends

DevOps Adoption Strategies: Principles, Processes, Tools, and Trends

4 (11)

Overview of this book

DevOps is a set of best practices enabling operations and development teams to work together to produce higher-quality work and, among other things, quicker releases. This book helps you to understand the fundamentals needed to get started with DevOps, and prepares you to start deploying technical tools confidently. You will start by learning the key steps for implementing successful DevOps transformations. The book will help you to understand how aspects of culture, people, and process are all connected, and that without any one of these elements DevOps is unlikely to be successful. As you make progress, you will discover how to measure and quantify the success of DevOps in your organization, along with exploring the pros and cons of the main tooling involved in DevOps. In the concluding chapters, you will learn about the latest trends in DevOps and find out how the tooling changes when you work with these specialties. By the end of this DevOps book, you will have gained a clear understanding of the connection between culture, people, and processes within DevOps, and learned why all three are critically important.
Table of Contents (18 chapters)
close
close
1
Section 1: Principles of DevOps and Agile
5
Section 2: Developing and Building a Successful DevOps Culture
8
Section 3: Driving Change and Maturing Your Processes
12
Section 4: Implementing and Deploying DevOps Tools

Iterating changes to processes

Just like with application code, it is important to take an iterative approach to changing processes. When it comes to application code, we take this approach so that if something does go wrong, we can easily know what changes were made, who made them, and why. It provides full traceability of what is happening.

We need that same level of traceability and transparency when it comes to iterating changes to processes. That way, if at any point we need to see what happened and why, it's easy to identify that information. Secondly, we can see the impact of a change before moving onto the next one.

This really applies to all types of changes, from technology processes to business processes. The biggest impact does not come with individual changes to those processes, but large programs of change that involve numerous changes to the same set of processes or the same process.

When we work in iterations, or in sprints as we commonly call them in...

Unlock full access

Continue reading for free

A Packt free trial gives you instant online access to our library of over 7000 practical eBooks and videos, constantly updated with the latest in tech

Create a Note

Modal Close icon
You need to login to use this feature.
notes
bookmark search playlist font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete

Delete Note

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete

Edit Note

Modal Close icon
Write a note (max 255 characters)
Cancel
Update Note

Confirmation

Modal Close icon
claim successful

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY