Progressive Delivery allows you to switch from high-stakes “big bang” releases to the gradual exposure of code changes in production. The goal is to observe changes in the health of your systems and user behavior before ramping up to your entire user population.
Early adopters of CD invented their own Progressive Delivery tooling and practices, freeing up their teams to move fast, limit the blast radius of issues found in production and focus engineering cycles on work that delivers more impact, not just more releases.
What can we learn from the ways these pioneers of Progressive Delivery implemented gradual release mechanisms and automated repeatable and trustworthy reporting of KPIs?
In this fast-moving talk, we’ll introduce the ideas and look at specific examples. We’ll sum up what we’ve seen by documenting the patterns in checklists you can take away to establish or extend these proven patterns in your own environment.