Why I love incremental delivery and why you should too
summary
A practical case: the ecosystems team implements automatic security fix pull requests for Maven despite complex resolution rules and parent POM overrides, then repeats for npm lockfiles, Yarn and NuGet, using short research spikes and customer feedback to avoid wasted work. The workflow is spike → build mini feature → measure with analytics and user conversations, with spikes timeboxed to half a day to a day and occasional hack weeks, yielding faster delivery, continuous learning and incremental reduction of complexity.
AI-written summary · about
chapters (5)
- 0:00Intro
- 1:29Dependency management
- 3:28Incremental delivery
- 7:50Incremental delivery for engineering
- 14:02Summary
related talks
55mContinuous Deployment Workflows for Modern JavaScript
59mThe continuous culture
38mBuilding a high quality product
41mContinuous delivery in 10 easy mistakes
45mContinuous Integration: That’s Not What They Meant
40mContinuous Delivery Anti-Patterns
24mManaging Dependencies with Confidence
01h 12mPitfalls of Continuous Deployment