Shift Left, Shift Right and Improve the Centre
summary
Continuous delivery is not just automation: a team transforms from bi-monthly releases with 24 production incidents into multiple deploys per day and only two production issues in a year by adding BDD, pair/mob programming, impact mapping, and testability work; production-side tools include logging tracing monitoring heatmaps and canary releases and rollbacks; a real case handles 250,000 concurrent users 30,000 bets per minute; testers become coaches and T‑shaped contributors (yes really 3 testers for 8 teams and 50 developers).
AI-written summary · about
chapters (11)
- 0:00Start
- 5:34Testers: what's your strategy in a continuous delivery context?
- 7:42What is CD?
- 8:22Some myths
- 9:07it does not work for complex systems
- 30:44Testing activities shift
- 33:14Improve the centre activities
- 33:39Shift Right activities
- 35:10How did 3 testers manage to do all this?
- 38:19Active Listening
- 38:51Empathy
related talks
49mThe Whole Team Approach to Testing in Continuous Delivery
42mTesting in a Continuous Delivery World
34mEnabling a Continuous Deployment Mindset
40mEmbracing Shift-Left Testing
41mContinuous delivery in 10 easy mistakes
01h 01mA team's transition to Continuous Delivery
32mClimbing the Mountain of CI/CD: A Tester’s Tale
59mThe continuous culture