Quality Engineering mindset and TBS
summary
Argues that quality engineering mindset is a company-wide cultural shift not just testers writing automation, and that a testing breakdown structure is a question-driven tool to define a concrete quality vision. Recommends focusing on actual constraints—workflows, documentation, CI pipelines, monitoring, security and performance—and measuring impact with fast feedback loops. Warns that chasing perfection stalls releases, that quality is ongoing (not a finished state), and that incremental, visible fixes win buy-in.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:24Quality engineering misconceptions
- 3:55Quality engineering principles
- 7:54QA to QE shift
- 9:40IT and business alignment
- 11:49Defining QE mindset
- 14:00Testers as quality ambassadors
- 16:33Neglecting quality pitfalls
- 17:59Testing breakdown structure
- 22:14Process and automation improvement
- 25:07Three key takeaways
- 26:34Q&A
related talks
50mThe End of Testing as We Know It
35mTesting != Quality
24mQuality Engineering: A Journey from traditional testing to ‘Shift-Left’ Mindset
09m"The Tester’s Role: Balancing Technical Acumen and User Advocacy"
35mWhy Software Engineers Should Make Quality a Priority
28mInstilling the built-in quality mindset into a dev team
09m“Leading a Testing Revolution”
34mesting in modern times: A story about quality and value