Applying Shift Left Test Strategy for Higher Quality
summary
Vanguard shifts testing earlier by running a 13-team pilot through coaching, dojos and training, adding two roles (product test engineer, automation engineer), and adopting Cucumber-based feature files, Pact contract tests, Sonar metrics and CI pipelines. Outcomes: regression suite shrinks, manual tests drop ~21%, testing cycle time falls from four to three weeks, production defects fall from thousands to hundreds, and 170 NGA teams reach twice‑monthly deploys.
AI-written summary · about
chapters (20)
- 0:00Introduction and speaker background
- 1:56Vanguard’s business and IT context
- 3:03From waterfall to agile transformation
- 4:53What is shift left testing?
- 6:49Role of Testing Center of Excellence
- 8:43People changes in shift left
- 10:11Process changes with BDD and TDD
- 10:55Technology and tooling updates
- 12:01Case study on shift left coaching
- 14:42Measuring shift left outcomes
- 16:38Automation strategy and investment
- 18:06Testing pyramid and manual tests
- 20:01Non-functional testing in pipeline
- 21:09Sustained coaching and results
- 22:25Benefits of shift left strategy
- 23:20Current state and future direction
- 25:17Q&A: Training and dojos
- 27:10Q&A: Separate testing teams
- 28:48Q&A: Cost savings and infrastructure
- 29:52Q&A: Shift right examples
related talks
40mEmbracing Shift-Left Testing
55mShifting the Testing Role Pendulum
01h 28mShift-Left Testing
15mQuality Engineering Journey from Shift Left to Shift Right and Beyond
53mTransforming testing methodologies: From manual to robust strategies
12mConvergent Quality Engineering
22mBuilding a Test Strategy that Scales
43mOne Strategy, One Community: A deep dive into a Global Testing Transformation