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
4. Treat your pipeline as a product for resiliency and fast feedback loops
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/13. Terminology

13. Terminology

Previous

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

Up next

14. References and further reading

In this chapter

13. Terminology