Get Your Evenings and Weekends Back: Release The Progressive Delivery Way

Logo
Presented by

Dave Karow Sr. Progressive Delivery Advocate, Split

About this talk

Gathering up changes and rolling them out all at once is the tired way to release. Teams that have switched to progressive delivery to release changes are able to ship smaller releases more often, without all the drama and time lost to incidents. Doing away with exhausting release nights and support ticket spikes, they've turned IT back into a "day job" and they've gotten their evenings and weekends back. Once you learn the progressive delivery model, the rest of the steps are intuitive and simple to execute. Come learn how! - Decouple deployment from release, so code can be deployed to production but kept "off" so it can be verified in production before being released to customers. - Control the gradual release of changes to customers without making any changes to that verified deployment and infrastructure configuration. - Observe *who* has been exposed to new code and watch for the differences in system health and user behavior for the "on" and "off" groups before rolling out to the entire user population.

Related topics:

More from this channel

Upcoming talks (1)
On-demand talks (9)
Subscribers (671)
Split's Feature Delivery Platform combines the safety and reliability of feature flags with data to measure the impact of every feature, so Product and Engineering teams can know the direct effect of their efforts on app performance, customer experience, and business goals. This shortens development cycles, mitigates release risk, and creates focus on the features that drive the greatest positive impact.