Achieving Weekly Releases: A Technical Deep Dive into Our Development Process
summary
Small six‑to‑seven person team ships 15 releases in 24 weeks by funneling feedback from Slack (700+ community), email, a public feature request page and UI research into Linear, using Linear projects that end, one ticket in progress per developer, and blocking-release tags to cut scope. No sprint estimates, optional async planning, pair programming and PR‑merging sessions speed reviews, automated staging/production deploys, and error alerts from Sentry and Crashlytics enforce quality while enabling weekly delivery and fast validation.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 2:20Company setup
- 3:25Challenges with Scrum
- 7:20Scrum hinders autonomy
- 8:24Alternative frameworks
- 9:28Capturing and funneling work
- 11:56User feedback tools
- 13:41Prioritizing features
- 16:53Weekly planning
- 19:00Task definition
- 20:04Speed versus quality
- 21:53Q&A
related talks
29mOur Journey to Fully Automated Weekly Releases
45mProject Release Planning: Building an Iterative Framework.
17mStreamlining Mobile Releases
38mBuilding a high quality product
36mIterative Mobile Development
30mIterative Mobile Development
28mHow we do developer productivity at Slack
47mI Deploy on Fridays (And Maybe You Should Too)