Team Guide to Software Releasability

Team Guide to Software Releasability

Manuel Pais and Chris O'Dell
This is a sample of the book's content.Buy on Leanpub

Table of Contents

Team Guide to Software Releasability

  • 1. Team Guides for Software
  • 2. Foreword
  • 3. Introduction
    • 3.1 What is software releasability?
    • 3.2 What constitutes a delivery system?
    • 3.3 What does resilient delivery feel like?
    • 3.4 Warning signs of software delivery debt
    • 3.5 Why invest in software releasability?
    • 3.6 Relationship to Continuous Delivery
    • 3.7 What this book is (not) about
    • 3.8 How to use this book
    • 3.9 Feedback and suggestions
  • 4. Treat your pipeline as a product for resiliency and fast feedback loops
    • 4.1 Make your pipeline the single route to production
    • 4.2 Your pipeline is now a product: invest in it
    • 4.3 Avoid simply retro-fitting CD into a CI server
    • 4.4 Measure delivery to visualize flow and identify bottlenecks
    • 4.5 Design the delivery system to evolve with your needs
    • 4.6 Apply monitoring and logging to minimize issues and downtime
    • 4.7 Scale the infrastructure to avoid pipelines queuing up
    • 4.8 Scale the practices and pipelines to support growing usage
    • 4.9 Care for pipeline testability and usability to encourage adoption
    • 4.10 Build security into and around the pipeline
    • 4.11 Get started!
    • 4.12 Summary
  • 5. Ensure delivery system is recoverable to endure disaster
  • 6. Ensure delivery system is operable to minimize downtime
  • 7. Ensure both practices and infrastructure can scale to meet usage growth
  • 8. Care for pipeline testability and usability to encourage adoption
  • 9. Measure delivery to visualize flow and identify bottlenecks
  • 10. Treat your pipeline as a value stream to tackle largest bottlenecks first
  • 11. Organize teams to promote build and release ownership
  • 12. Appendix A: build security into and around the pipeline
  • 13. Terminology
  • 14. References and further reading
    • 14.1 Introduction
    • 14.2 Chapter 1 - Treat Your Pipeline as a Product
  • 15. About the authors
    • 15.1 Chris O’Dell
    • 15.2 Manuel Pais
  • 16. Conflux Books
Team Guide to Software Releasability/overview

Team Guide to Software Releasability

course_overview

Software releasability means not only being able to deploy faster, but also being able to quickly recover from disaster and adapt to business challenges.

count_chapters
begin_reading
download
p_implied_book_part_name

Team Guide to Software Releasability16 chapters

Begin ›
  1. 1. Team Guides for Software

  2. 2. Foreword

  3. 3. Introduction

  4. 4. Treat your pipeline as a product for resiliency and fast feedback loops

  5. 5. Ensure delivery system is recoverable to endure disaster

  6. 6. Ensure delivery system is operable to minimize downtime

  7. 7. Ensure both practices and infrastructure can scale to meet usage growth

  8. 8. Care for pipeline testability and usability to encourage adoption

  9. 9. Measure delivery to visualize flow and identify bottlenecks

  10. 10. Treat your pipeline as a value stream to tackle largest bottlenecks first

  11. 11. Organize teams to promote build and release ownership

  12. 12. Appendix A: build security into and around the pipeline

  13. 13. Terminology

  14. 14. References and further reading

  15. 15. About the authors

  16. 16. Conflux Books