Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Continuous Delivery and DevOps ??? A Quickstart Guide
  • Toc
  • feedback
Continuous Delivery and DevOps ??? A Quickstart Guide

Continuous Delivery and DevOps ??? A Quickstart Guide

By : Paul Swartout
5 (1)
close
Continuous Delivery and DevOps ??? A Quickstart Guide

Continuous Delivery and DevOps ??? A Quickstart Guide

5 (1)
By: Paul Swartout

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
Table of Contents (13 chapters)
close

Standardizing vocabulary and language

One small and wholly avoidable thing that can scupper any project is the misinterpretation or confusion of what the deliverables are. This may sound a little alarming, but projects can fail simply because one person expects something, but another person misunderstands or misinterprets and delivers something else. It's not normally down to ignorance; it's normally due to both sides interpreting the same thing in different ways.

For example, let's look at something relatively innocuous; the word release. To a project manager or a release manager, this could represent a bundle of software changes, which need to be tested and put live within a schedule or program of work. This will normally entail detailed project plans, close coordination with all departments inside and outside of the product delivery function and lots of meetings...

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
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