Culture of Continue Delivery

on YouTube ↗33m

" summary

Claim: adopting XP practices and a CI/CD pipeline turns stalled six-month projects into rapid, tested releases. Evidence: 100+ story cards and a waterfall habit cause last‑minute weekends and flop launches; switching to test‑driven dev, mainline commits, and a build pipeline yields fewer bugs, predictable Feature Toggles, repeatable deploys by button, and Automated tests that catch regressions. A field build shows a 50% battery drop fixed by remote shutdown and longer cables proving the approach works with automated build & deployment scripts.

AI-written summary · about

" chapters (10)

1. 0:00Introduction
2. 1:53Agenda
3. 3:10Story
4. 5:38Water and Fall
5. 7:08Fix That Fast
6. 12:45Autonomy
7. 16:36Engineering Practices
8. 20:33Continuous Improvement
9. 23:30Summary
10. 26:27Neuroscience

" related talks

• 59mThe continuous cultureKim van Wilgen · Build Stuff 2017
• 40mContinuous Delivery Anti-PatternsJeff Morgan · Agile Testing Days 2016
• 31mThe Continuous CultureKim van Wilgen · The Lead Developer New York 2018
• 40mSustainable Continuous Delivery: Patterns for rapid and reliable ReleasesManuel Pais · DevOpsCon Spring 2019
• 01h 01mA team's transition to Continuous DeliveryAshley Noble · NDC Sydney 2017
• 33mSoftware development practices for companies that want to make an impactYuval Pemper · Nerdearla 2020
• 47mContinuous Delivery WarstoriesAllan Ebdrup · GOTO Copenhagen 2015
• 51mBetter software, faster: principles of Continuous Delivery and DevOpsBert Jan Schrijver · Devoxx Belgium 2019