Practical Ideas on Building Quality Culture
summary
QA drives concrete changes: set up custom ADO/Gyra risk items and attach them to releases, build dashboards showing traceability and burndown, and score bugs to extract cost‑to‑fix so leaders see money and risk. Run monthly bug clinics and Batman emergency teams to prevent repeats and create ownership. Use the two‑dimensional Gyra filter to assess release readiness. These practices produce measurable shifts left, clearer responsibilities, more collaboration with devs and PO, and noticeably fewer late surprises.
AI-written summary · about
chapters (23)
- 0:00Quality culture in QA
- 3:42Violated processes and responsibility
- 7:21Quality culture beyond processes
- 9:05Engaging stakeholders for quality values
- 12:17Leadership support with data and risks
- 15:57Tracking releases and risks
- 17:22Bug tracking for prevention
- 19:12Behavior and rules in testing
- 22:43Shift testing left with metrics
- 25:38Fixing pain points for trust
- 27:02Auto tests as product artifacts
- 28:11Quality advocates and heroes
- 30:02Knowledge gaps in quality
- 31:45Batman team for incidents
- 33:28Knowledge sharing communities
- 34:10QAs driving change with data
- 35:13Q&A: Process vs mindset
- 36:19Q&A: Resistance to changes
- 38:32Q&A: Poor user stories from POs
- 39:58Q&A: Metrics-only syndrome
- 41:01Q&A: Convincing non-tech managers
- 42:30Q&A: Detailed tracking bureaucracy
- 44:00Summary
related talks
40mAmplifying Agile Quality Practices
28mInstilling the built-in quality mindset into a dev team
42mImproving Testing Quality by Changing Culture
16mTear Down the QA Wall
40mReal Quality Assurance from an Agile and Lean Viewpoint
31mAssembling Excellence: Crafting a Quality Assurance Team from the Ground Up
53mBest-Practice Quality Assurance for Small Teams
41mQuality Transformation