“When can we make a release?”
summary
Claim: the single determinant for making a release is confidence. It increases by four concrete capabilities: omni testing (continuous, cross-role tests and conversations to raise information), CI/CD that shortens feedback loops and removes build uncertainty, an ongoing risk mindset (not one-off analysis), and a rollback capability via monitoring/observability/operability. Warnings: separate automation teams, static risk lists, or skipping rollbacks create silos and false confidence. Release becomes possible anytime once those are in place.
AI-written summary · about
chapters (9)
- 0:00Intro
- 0:14We are uncertain
- 0:38What releasing means
- 1:42When can we make a release
- 2:15What stop us
- 2:54Improving confidence
- 3:44Enable CICD
- 4:28Have a risk mindset
- 5:19Roll back
related talks
33mTESTING IN PRODUCTION
46mTesting Times in 2021: Delivering with Confidence
32mBuilding Confidence Together: Continuous Integration & Testing
25mTesting in Production
41mShift Left, Shift Right and Improve the Centre
23mA little less testing, a little more quality
36mTesting In Production
19mBusiness Impact Delivery Using Test Automation