Progressive delivery enhances continuous delivery by deploying software to a subset of users for evaluation before a broader rollout. It emphasizes a culture of experimentation, fine-grained control, and delegation, allowing developers to manage feature releases and user impacts gradually. Key concepts include feature flags, observability, and integrating user experience with software metrics.

1. An introduction to
Progressive Delivery
James Governor, RedMonk co-founder

6. “What if it were possible
to ship software on a
Friday?”
Casey West, Google Cloud Platform

7. CI/CD

8. Agile

17. developer
experience

31. content
marketing

33. conversion
rates

35. Progressive Delivery is the next step after
continuous delivery, where new versions are
deployed to a subset of users and are
evaluated in terms of correctness and
performance before rolling them to the totality
of users
– Carlos Sanchez

36. fine-grained control over the blast radius

37. growth
hacking
software
delivery

40. Progressive
Delivery

41. A culture of
Experimentati
on

42. deploy!=releas
e

43. Release Progression – progressively increasing the
number of users that are able to see (and are
impacted by) new features.
Delegation – progressively delegating the control
of the feature to the owner that is most closely
responsible for the outcome.
definitions by Adam Zimman (Launch Darkly).

44. Pete Hodgson @ph1 at martinfowler.com

46. Configuratio
n as Code

47. Observabilit
y

52. UX

53. Automate
Everything

54. Instrument
Everything

55. Measure
Everything

56. Subbu Allamaraju, Expedia: https://m.subbu.org/incidents-trends-from-the-trenches-

57. subbu.org
Subbu Allamaraju’s Blog

58. product
manageme
nt

60. As ever, it’s a culture problem
Bringing growth hacking ideas to software delivery
Feature flags are the bridge
Feedback loops – observability
Observability and User experience
Bringing together metrics
• software delivery
• UX
• infrastructure
Feature Experimentation with managed risk
Testing in Production, to segmented user populations