Team Guide to Software Releasability
This book is 20% complete
Last updated on 2018-07-11
About the Book
The last book in the 'Team Guide' collection from Skelton Thatcher Publications.
Strong build & release engineering capabilities are key to rapid and reliable delivery of modern software systems. Learn how software releasability means not only being able to deploy faster, but also being able to quickly recover from disaster and adapt to changing technical and business challenges.
The ‘Team Guide’ collection is designed to help teams building and running software systems to be as effective as possible. Guides are curated by experienced practitioners and emphasise the need for collaboration and learning, with the team at the centre.
About the Authors
About the Contributors
Manuel Pais is an independent DevOps and Delivery Consultant, focused on teams and flow.
With a diverse experience including development, build management, testing and QA, Manuel has helped large organizations in finance, legal, and manufacturing adopt test automation and continuous delivery, as well as understand DevOps from both technical and human perspectives.
Manuel is co-author of the Team Guide to Software Releasability book and lead editor for the remaining books in the Team Guide series.
Table of Contents
- The Team Guide series
- Foreword
-
Introduction
- What is software releasability?
- What constitutes a delivery system?
- What does resilient delivery feel like?
- Warning signs of software delivery debt
- Why invest in software releasability?
- Relationship to Continuous Delivery
- What this book is (not) about
- How to use this book
- Feedback and suggestions
-
1. Treat your pipeline as a product for resiliency and fast feedback loops
- 1.1 Make your pipeline the single route to production
- 1.2 Your pipeline is now a product: invest in it
- 1.3 Avoid simply retro-fitting CD into a CI server
- 1.4 Measure delivery to visualize flow and identify bottlenecks
- 1.5 Design the delivery system to evolve with your needs
- 1.6 Apply monitoring and logging to minimize issues and downtime
- 1.7 Scale the infrastructure to avoid pipelines queuing up
- 1.8 Scale the practices and pipelines to support growing usage
- 1.9 Care for pipeline testability and usability to encourage adoption
- 1.10 Build security into and around the pipeline
- 1.11 Get started!
- 1.12 Summary
- 2. Ensure delivery system is recoverable to endure disaster
- 3. Ensure delivery system is operable to minimize downtime
- 4. Ensure both practices and infrastructure can scale to meet usage growth
- 5. Care for pipeline testability and usability to encourage adoption
- 6. Measure delivery to visualize flow and identify bottlenecks
- 7. Treat your pipeline as a value stream to tackle largest bottlenecks first
- 8. Organize teams to promote build and release ownership
- 9. Appendix A: build security into and around the pipeline
- Terminology
-
References and further reading
- Introduction
- Chapter 1 - Treat Your Pipeline as a Product
-
About the authors
- Chris O’Dell
- Manuel Pais
About the Publisher
This book is published on Leanpub by Skelton Thatcher Publications
Developing and running modern software systems requires teams of motivated and well-trained people; however, most IT books are written for the individual technologist. The Team Guide series from Skelton Thatcher Publications takes a team-first approach to software systems with the aim of empowering whole teams to build and operate software systems more effectively.
The Leanpub 45-day 100% Happiness Guarantee
Within 45 days of purchase you can get a 100% refund on any Leanpub purchase, in two clicks.
See full terms...
