Continuous Delivery Warstories
summary
Debitoor moves from 14‑day sprints to Continuous Deployment, claiming deploy 10 times a day and cutting mean bug-to-prod time to nine minutes in an example. Workflow uses short feature branches merged by TeamCity via ready/ branch queue* into a single long‑lived master; GitHub pull‑request deploys run on Heroku. QA and ops roles shrink as developers own deploys, backed by New Relic monitoring. Reported outcomes: developers spend 91% of time coding, ~140% throughput, defects down 44% and roughly half the previous cost.
AI-written summary · about
chapters (11)
- 0:00Start
- 3:29Speed
- 5:03Price
- 5:21Recruiting
- 10:14Manual processes like: Manual tests Code reviews
- 10:32Meetings
- 11:00Waiting
- 11:26Handovers
- 11:47Gates
- 12:57Complexity
- 13:39Big scope
related talks
01h 01mA team's transition to Continuous Delivery
55mThe Rationale for Continuous Delivery
46mContinuous Deployment Workflows
40mContinuous Delivery Anti-Patterns
51mBetter software, faster: principles of Continuous Delivery and DevOps
28mClimbing the Mountain of CI/CD: A Tester’s Tale
34mEnabling a Continuous Deployment Mindset
33mContinuous Delivery - What does good really look like?