Progressive Delivery
summary
Progressive delivery argues that shipping faster is not enough and claims decoupling building from user-facing change reduces the “jerk” that breaks workflows; it prescribes feature flags and staged progressive rollouts plus observability to measure clicks, dwell time and error rates so teams can avoid rolling a change to 100% that 50% of users hate. It organizes capabilities into abundance, autonomy, alignment, automation and pushes radical delegation so control over who sees features lives close to the user.
AI-written summary · about
chapters (10)
- 0:00Progressive delivery intro
- 1:27Authors and their book
- 3:12Jerk in software changes
- 7:07Four factors of delivery
- 13:32From waterfall to progressive
- 15:17Progressive rollout core
- 17:46Radical delegation
- 20:35Users in DevOps cycle
- 23:04Users as co-creators
- 24:07Conclusion
related talks
49mCustomize Progressive Delivery for Your Own Workload and Traffic
29mPlug-and-Play Progressive Delivery for Kubernetes Built-in Workloads With OpenKrui...
14mGaining speed
12mPredictable is better than fast
40mDeveloping at Cruise Speed
23mA little less testing, a little more quality
30mDoes Progressive Enhancement Have a Place in Today's Web?
49mDelivering incrementally: lessons about breaking up complex features