You're reading from Embracing DevOps Release Management Strategies and tools to accelerate continuous delivery and ensure quality software deployment

Product type Paperback

Published in Apr 2024

Publisher Packt

ISBN-13 9781835461853

Length 350 pages

Edition 1st Edition

Tools

Construct

Concepts

Continuous Delivery

Author (1):

Joel Kruger

Preface

1. Part 1: Understanding the Software Development Life Cycle and Its Design

2. Chapter 1: Understanding the Software Development Life Cycle FREE CHAPTER

3. Chapter 2: A Brief Introduction to Release Management

4. Chapter 3: What Are the Various SDLC Release Management Models?

5. Part 2: The Advantages of DevOps Release Management

6. Chapter 4: What Problems Does DevOps Release Management Try to Solve?

7. Chapter 5: Understanding What Makes DevOps Release Management Unique

8. Chapter 6: Understanding the Basics of CI/CD

9. Chapter 7: A Practical Pipeline for Technical Release Managers

10. Chapter 8: How CI/CD Pipelines Enforce Good DevOps Release Management

11. Part 3: Develop a Culture of DevOps in Your Organization’s Release Management Strategy

12. Chapter 9: Embracing DevOps Culture in Your Release Management Strategy

13. Chapter 10: What Does Receiving Support from Leadership and Stakeholders Look Like?

14. Chapter 11: Overcoming Common Pitfalls in DevOps Release Management

15. Index

16. Other Books You May Enjoy

Appendix

Questions

Answer the following questions to test your knowledge of this chapter:

What is a change management strategy intended for?
What are the elements of a change proposal and what is its purpose?
What are the elements of a change log and what is its purpose?
What is a release checklist and what is its intended purpose?
What is the secret ingredient to any successful DevOps transformation?
Why is it false to think that DevOps is mainly about tools?
What are three kinds of metrics that DevOps release managers should stridently avoid tracking?
Briefly, what are the seven steps in the monolithic-to-microservices roadmap?
Is it true that the use of CI/CD pipelines means that a company is successfully applying DevOps practices?
What is the single most critical reason why it is a mistake to assume that a quiet customer is a happy customer?

The rest of the chapter is locked