Learn release management best-practices with Azure Well-Architected Framework

Robby Millsap joins David Blank-Edelman in this second part in this series to discuss ways to reduce toil and friction using best practices from the Operational Excellence pillar of the Azure Well-Architected Framework.


[00:00] Introduction
[02:22] How can Operational Excellence address some of the problems we're having in our release cycle?
[02:10] How can we reduce toil?
[02:55] How can we optimize our release process?
[03:34] How can automation and just-in-time permissions help us reduce toil?
[04:19] What are some of the other benefits of automation?
[05:14] What are some other ways we can reduce friction in our deployments?
[06:23] What are some methods for reducing configuration drift?
[07:30] Apart from unit tests, what other types of tests should we be running?
[08:09] How can we decrease unexpected faults once we deploy?
[08:54] What's the best way to avoid those "down for maintenance" screens when we're deploying new code?
[09:50] How can I avoid having to replicate my entire production environment to facilitate blue and green deployments?
[10:15] Where can I go to learn more about the Well-Architected Framework?

📺 Related Episodes:

🔴 Watch more episodes in the Azure Well-Architected Series

🔴 Explore more cloud enablement resources