Continuous Delivery and DevOps - A Quickstart Guide 2nd Ed.

Deliver Quality Software Regularly and Painlessly by Adopting CD and DevOps

Paul Swartout

Publisher: Packt, 2014, 179 pages

ISBN: 978-1-78439-931-3

Keywords: DevOps

Last modified: May 20, 2021, 5:43 p.m.

Continuous Delivery (CD) and DevOps are fast becoming the next big thing(s) in relation to the delivery and support of software.

This updated edition provides you with a clear and concise insight in to what CD and DevOps are all about, how to go about preparing for and implementing them, and what quantifiable business value they bring.

You will be guided through the various stages of CD and DevOps adoption, the impact they will have on you and your business, how you can overcome common problems, and what to do once CD and DevOps have become embedded in your ways of working.

Included within are some real-world examples, tricks, tips, and observations that should help ease the adoption and allow you to fully utilize CD and DevOps to deliver quality software.

  1. Evolution of a Software House
    • A brief history of ACME systems
    • ACME systems version 1.0
      • Software delivery process flow version 1.0
    • ACME systems version 2.0
      • Software delivery process flow version 2.0
      • A few brave men and women
    • ACME systems version 3.0
      • Software delivery process flow version 3.0
    • ACME systems version 4.0
    • The evolution in a nutshell
    • Summary
  2. No Pain, No Gain
    • Elephant in the room
    • Defining the rules
    • Including (almost) everyone
      • Identifying the key people
      • Too many cooks
    • Openness, transparency, and honesty
      • Location, location, location
      • It's all happy-clappy management waffle – isn't it?
    • The great elephant disclosure
      • Value stream mapping
    • Summary
  3. Plan of Attack
    • Setting and communicating the goal and vision
    • Standardizing vocabulary and language
    • A business change project in its own right
    • The merits of a dedicated team
      • Who to include
    • The importance of evangelism
    • Courage and determination
    • Understanding the cost
    • Seeking advice from others
    • Summary
  4. Culture and Behaviors
    • All roads lead to culture
    • An open, honest, and safe environment
      • Openness and honesty
      • Courageous dialogue
      • The physical environment
    • Encouraging and embracing collaboration
    • Fostering innovation and accountability at grass roots
    • The blame culture
      • Blame slow, learn quickly
    • Building trust-based relationships across organizational boundaries
    • Rewarding good behaviors and success
      • The odd few
    • Recognizing dev and ops teams are incentivized can have an impact
    • Embracing change and reducing risk
      • Changing people's perceptions with pudding
    • Being transparent
    • Summary
  5. Approaches, Tools, and Techniques
    • Engineering best practice
      • Source control
      • Small, frequent, and simple changes
      • Never break your consumer
      • Open and honest peer-working practices
      • Fail fast and often
      • Automated builds and tests
      • Continuous Integration
      • Using the same binary across all environments
    • How many environments are enough?
    • Developing against a production-like environment
    • CD tooling
      • Automated provisioning
      • No-downtime deployments
    • The cloud
    • Monitoring
    • When a simple manual process is also an effective tool
    • Summary
  6. Hurdles Along the Way
    • What are the potential issues you need to look out for?
      • Dissenters in the ranks
        • No news is no news
        • The anti-agile brigade
      • The transition curve
      • The outsiders
      • Corporate guidelines, red tape, and standards
      • Geographically diverse teams
      • Failure during evolution
      • Processes that are not repeatable
      • Recruitment
    • Summary
  7. Vital Measurements
    • Measuring effective engineering best practice
      • Simple quality metrics
      • Code complexity
      • Unit test coverage
      • Commit rates
      • Adherence to coding rules and standards
      • Where to start and why bother?
    • Measuring the real world
      • Measuring the stability of the environments
        • Incorporating automated tests
        • Combining automated tests and system monitoring
        • Real-time monitoring of the software itself
        • Monitoring utopia
      • Effectiveness of CD and DevOps
      • Impact of CD and DevOps
      • Measuring your culture
    • Summary
  8. Are We There Yet?
    • Reflect on where you are now
    • Streaming
    • A victim of your own success
    • [P]lan, [D]o, [C]heck, [A]djust
    • Exit stage left
    • Rest on your laurels (not)
    • Summary
  9. The Future is Bright
    • Expanding your horizon
      • Reactive performance and load testing
      • Reducing feature flag complexity
      • Easing A/B testing
      • Security patching and saving your bacon
      • Order out of chaos monkey
      • End user self-service
      • CD and DevOps and the mobile world
    • Expanding beyond software delivery
    • What about me?
    • What have you learned?
    • Summary
    1. Some Useful Information
      • Tools
      • People
      • Recommended reading
    2. Where Am I on the Evolutionary Scale?

  1. Retrospective Games
    • The timeline game
    • StoStaKee
  2. Vital Measurements Expanded
    • Code complexity – some science
    • Code versus comments
    • Embedding monitoring into your software


Continuous Delivery and DevOps - A Quickstart Guide

Reviewed by Roland Buresund

Very Good ******** (8 out of 10)

Last modified: Nov. 12, 2023, 1:51 a.m.

A very good introduction to CD, DevOps and Agile. It doesn't cover stuff in detail but touches on nearly all important point that anyone needs to have an understanding of.

Be aware that it is written by committed Agile people, so the approach to anyone that dares voice concerns over anything is old and not willing to change (they even cover Change of staff in the book).

All in all, an enjoyable read and recommended if you want some (admittedly technical) understanding of the books topics.


There are currently no comments

New Comment


required (not published)