Step-by-step guide to safely introducing high-risk changes in your software system

Thanks for your comment. I think that could be set of proper references to dive deep into the topic:

"Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation" by Jez Humble and David Farley. This book covers various techniques for safely introducing changes, including gradual rollout, feature flags, and canary releases.

"Release It!: Design and Deploy Production-Ready Software" by Michael T. Nygard. This book provides practical advice on how to design and deploy reliable and resilient software, including techniques for gradually introducing changes and mitigating risks.

"Deploying Machine Learning Models: A Practical Guide to Building, Testing, and Managing Production-Ready Models" by Sayak Paul and Amit Chaudhary. This book focuses specifically on the deployment of machine learning models and covers techniques such as canary releases and A/B testing.

"Testing in Production" by Cindy Sridharan. This article provides an in-depth exploration of the concept of testing in production, including the use of feature flags and canary releases.

"Feature Toggles (aka Feature Flags)" by Martin Fowler. This article provides an overview of the concept of feature toggles and how they can be used to safely introduce changes