Software Delivered

Your system’s architecture can support team autonomy, independent deployability, and independent evolution of components, or it can be a sticky mess. This episode looks at whether choosing a monolith or microservices fundamentally changes the crucial properties of your architecture. Listen to find out more about: Episode details You can also watch episodes on YouTube.

Your branching strategy can support Continuous Delivery, or make it an impossible goal. Teams should assess the impact of how they branch on their ability to deliver software at all times, and that means there are some branching techniques that make software delivery more like walking in the dark through a field of rakes. Listen […]

To ensure software is deployable, teams must shift from manual testing to automated pipelines. Automation provides immediate feedback, captures institutional knowledge, and reduces long-term costs. Strategies like the Strangler Pattern help modernize legacy code for greater reliability. Listen to find out more about: Episode map You can also watch episodes on YouTube.

Tony Kelly hosts our first episode of Continuous Delivery Office Hours, with Bob Walker and Steve Fenton. In this episode of Continuous Delivery Office Hours, we ponder why prioritizing Continuous Delivery (CD) is essential for managing risk. We challenge the common instinct to reduce deployment frequency after failures, using a dentist analogy to explain how […]