Book Overview & Buying
Table Of Contents
Feedback & Rating

Continuous Delivery and DevOps ??? A Quickstart Guide

By : Paul Swartout

5 (1)

Buy this Book

Continuous Delivery and DevOps ??? A Quickstart Guide

5 (1)

By: Paul Swartout

Buy this Book

Overview of this book

Over the past few years, Continuous Delivery (CD) and DevOps have been in the spotlight in tech media, at conferences, and in boardrooms alike. Many articles and books have been written covering the technical aspects of CD and DevOps, yet the vast majority of the industry doesn’t fully understand what they actually are and how, if adopted correctly they can help organizations drastically change the way they deliver value. This book will help you figure out how CD and DevOps can help you to optimize, streamline, and improve the way you work to consistently deliver quality software. In this edition, you’ll be introduced to modern tools, techniques, and examples to help you understand what the adoption of CD and DevOps entails. It provides clear and concise insights in to what CD and DevOps are all about, how to go about both preparing for and adopting them, and what quantifiable value they bring. You will be guided through the various stages of adoption, the impact they will have on your business and those working within it, how to overcome common problems, and what to do once CD and DevOps have become truly embedded. Included within this book are some real-world examples, tricks, and tips that will help ease the adoption process and allow you to fully utilize the power of CD and DevOps

Preface

Who this book is for

What this book covers

To get the most out of this book

Get in touch

Free Chapter

The Evolution of Software Delivery

ACME systems – evolution phase 1.0

ACME systems evolution phase 2.0

ACME systems evolution phase 3.0

ACME systems beyond Version 3.0

The evolution in a nutshell

Where am I on the evolutionary scale?

Summary

Understanding Your Current Pain Points

Elephant in the room

Defining the rules

Including (almost) everyone

Openness, transparency, and honesty

The great elephant disclosure

Summary

Culture and Behaviors are the Cornerstones to Success

All roads lead to culture

An open, honest, and safe environment

Encouraging and embracing collaboration

Fostering innovation and accountability at a grass-roots level

The blame game

Building trust-based relationships across organizational boundaries

Rewarding good behaviors and success

Recognizing how Dev and Ops teams are incentivized can have an impact

Embracing change and reducing risk

Being transparent

Summary

Planning for Success

Some common problems

Setting and communicating goals and vision

Standardizing vocabulary and language

A business change project in its own right

The importance of evangelism

Seeking advice from others

Summary

Approaches, Tools, and Techniques

Engineering best practices

Continuous integration

Summary

Avoiding Hurdles

What are the potential issues you need to look out for?

Corporate guidelines, red tape, and standards

Geographically diverse teams

Failure during the evolution

Processes that are not repeatable

Bridging the skills gap

Changes in leadership

Summary

Vital Measurements

Measuring effective engineering best practices

Summary

You Are Not Finished Just Yet

Reflecting on where you are now

Streaming

A victim of your own success

[P]lan, [D]o, [C]heck, [A]djust

Resting on your laurels (not)

Summary

Expanding Your Opportunity Horizon

What about me?

Performance and load-testing

Reducing feature-flag complexity

A/B testing

Blue-green deployments

Security-patching and bacon-saving

Order-out-of-chaos monkey

End user self-service

Thing as a service

Summary

CD and DevOps Beyond Traditional Software Delivery

CD, DevOps, and the mobile world

What about me?

What have you learned?

Summary

Some Useful Information

Tools

People

All roads lead to culture

There are many people in the tech industry—some very influential—who believe that the adoption of CD and/or DevOps simply amounts to implementing some technical tools and then making slight tweaks to existing heavyweight processes to potentially allow software to be released every few weeks/months.

Worse still, some see this as a bona fide reason to set up a new DevOps team inside the existing organization that—all things considered—spend their time building and implementing tools and processes that make little or no difference to successful delivery of quality software.

If you believe these views to be correct, then you are simply wrong at best and delusional at worst. Just to reiterate, CD and DevOps are—put very simply—agile ways of working. The DevOps tools are just that—tools. When we say ways of...